another easy target for the trigger would be the updates sync that runs on releng04... it's currently a every 30min cron... it could be a fedmsg triggered from bodhi thing
This is referring to the following puppet script:
puppet/configs/system/fedora-updates-push
We have a new version of that script now, but it still runs from cron, not fedmsg.
:broken_heart:
We still definitely want to do this.
Metadata Update from @kevin: - Assignee reset - Issue priority set to: Waiting on Asignee
Metadata Update from @kevin: - Issue priority set to: Next Meeting (was: Waiting on Assignee)
So, in todays meeting we decided to just fix this so it runs from cron every minute (since it now can see if it needs to do anything and exit in a second or two if it doesn't).
:goat:
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.