Describe what you need us to do: Currently we only keep the last version of any srpm in our infra tags in koji, this means, if you push an update and for some reason need to downgrade, you'll have to untag the new build, wait some time for the repo to be re-generated and then you can downgrade. Keeping the last 2 or 3 builds for every srpm would allow for a much quicker rollback when things go sideways.
When do you need this? (YYYY/MM/DD) No ETA
When is this no longer needed or useful? (YYYY/MM/DD) When we stop using RPMs/this tag in koji
If we cannot complete your request, what is the impact? Longer time to rollback, higher chances to poke at ops folks for help rather than allowing to downgrade and reschedule
Metadata Update from @mizdebsk: - Issue untagged with: koji - Issue assigned to mizdebsk - Issue tagged with: bodhi
This is blocked by #7273
PR submitted: https://pagure.io/releng/tag2distrepo/pull-request/1
Metadata Update from @mizdebsk: - Issue priority set to: Waiting on External (was: Waiting on Assignee)
There has been no upstream response in 7 days, so I'm going to apply the patch downstream.
Metadata Update from @mizdebsk: - Issue priority set to: Waiting on Assignee (was: Waiting on External)
python-tag2distrepo (fedmsg listener) part of this feature was implemented in build python-tag2distrepo-1-0.9.fc29, dist-repo-regen (cron job) part was implemented in ansible commit 2809512f. Both changes are now deployed in production.
I've also manually triggered regeneration of all dist repos.
Metadata Update from @mizdebsk: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Metadata Update from @mizdebsk: - Issue priority set to: None (was: Waiting on Assignee)
Login to comment on this ticket.