CloudSIG is preparing a new big push to cloud8-openstack-wallaby-testing including 372 packages. The tagging scripts takes package and serially will untag each one from -candidate and tag it into a testing.
In the past, similar situations lead to overload the sign and push automation and it was disabled to run the tagging scripts. The aim of this issue is to coordinate this time.
BTW, what'd be the recommendation to do massive tagging with low impact on the sign and push system?, we may be able to improve our tooling if needed.
Metadata Update from @arrfab: - Issue assigned to arrfab - Issue priority set to: Waiting on Reporter (was: Needs Review) - Issue tagged with: cbs, low-gain, low-trouble
Metadata Update from @arrfab: - Issue tagged with: centos-common-infra
We can do what we have done earlier for the official cloud8-openstack-victoria-release tag :
Do you have a date in mind ?
Could it be at some point today, October, 8th?
@amoralej : sure ! I'll have some meetings today but if we can do this in the morning, that would be perfect (and we can sync in #centos-devel , as usual ;-) )
Done and -testing was processed and pushed out.
Metadata Update from @arrfab: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
There has been some work in Koji to make this less painful. The tagBuildBypass() RPC defaults to "False" now (https://pagure.io/koji/issue/2292). See the --notify option to koji clone-tag.
tagBuildBypass()
--notify
koji clone-tag
Login to comment on this ticket.