Learn more about these different git repos.
Other Git URLs
Right now we have a list of releng folks that trade off weekly handling bodhi updates pushes. Because all these folks are in different locations and have different workdays and business, updates pushes happen as they are able throughout the day. Additionally some folks are able to push on weekends and holidays and others are not.
Since we no longer need a human release engineer to sign packages before pushing updates, we should consider moving this to just a cron script that runs at the same time every day. This would have the advantage of making the pushes much more predictable and would also save time of busy release engineers.
The script would need to have a bit of error handling and check for existing lock files and error out if any exist. It would also need to be adjustable during freezes to not push the stable updates for the frozen release. Any issues or problems would need to follow a process of filing a ticket on the issue and all release engineers communicating on that ticket so no one is duplicating efforts.
Metadata Update from @ausil: - Issue assigned to kellin
This really needs to be tied into fedmsg and be triggered based on events. perhaps with some systemd tieins to ensure that they happen regullary enough and then all tied in to FMN to get notifications to the right people when things go wrong. I have a strong desire to not use cron as it does not provide a good feedback loop
@ausil What event would have you it trigger on?
@mattdm that there is something to go stable. time since last push. main issue with cron is that the failure essentailly goes to /dev/null and no one looks at it until someone complains that things have not worked. like rawhide for the last 10 days
@ausil but won't that be also the case with fedmsg-driven trigger?
Duplicate of https://taiga.fedorainfracloud.org/project/acarter-fedora-docker-atomic-tooling/us/1010?kanban-status=145 since this is an RFE not a break-fix.
Closing.
Metadata Update from @syeghiay: - Issue close_status updated to: Duplicate - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.