action #52094
closed
Added by lnussel almost 5 years ago.
Updated over 4 years ago.
Category:
Release Engineering
Description
enable bots and tools
- totest manager
- origin-manager (jimmy)
- snapshot announcer (make sure to fix links in the template)
- manager_42 (probably obsoleted by origin-manager -> jimmy)
- update_crawler (may also be replaced by origin-manager)
- build fail reminder
- staging bot (jimmy)
- openqa commments (has a different name now, ask jimmy)
- duplicate binaries
- support package rebuild
- package list generator
Add the new release to
- Description updated (diff)
- Due date changed from 2020-01-23 to 2019-06-21
- Start date changed from 2019-06-06 to 2019-05-29
- Start date changed from 2019-05-29 to 2019-06-03
- Description updated (diff)
- Status changed from New to In Progress
I did email Jimmy, Coolo and Max.
Unfortunately it seems that I do not have permissions to edit bots on botmaster.suse.de
From the list above only two need config ported for 15.2 and the rest should either already be enabled or need to be pointed at 15.2. This used to involve systemctl enable a few times, but it is now in gocd which is coolo's world. I created a PR#2130 to port the announcer and manager_42 configs.
As can be seen by request#716125 origin-manager is already running as I created the OSRT:OriginConfig attribute on both 15.2 and 15.2:NonFree a while ago.
To ensure the rest of configured bump coolo regarding gocd.
I added staging-bot permission to 000product, 000release-packages and 000update-repos; added leaper permission to 00Meta.
- Due date changed from 2019-06-21 to 2019-08-09
Are we done with this? Max, Jimmy, could you please update the description of the issue to reflect what you did? Use strike through tags to mark tools as done that are done.
- Checklist item changed from to [x] totest-manager, [x] origin manager, [x] manager_42, [ ] build fail reminder, [x] staging-bot, [x] support packages rebuild, [x] pkglistgen, [x] trigger rebuild, [ ] duplicate binaries, [ ] openqa comments
duplicated binaries and build fail reminder is now only running for Factory.
not sure about openqa comments.
- Checklist item changed from to [x] openqa comments
openqa comments is now staging-report which is running
I thought coolo had merged this into "repo-checker" when he copy/pasted the code around, but it is unclear if that happened since it seems to still be running.
- Due date changed from 2019-08-09 to 2019-08-21
- Assignee changed from mlin7442 to coolo
- % Done changed from 0 to 90
ok thanks, so leaving for coolo when he is back
- Checklist item changed from to [x] duplicate binaries
- Due date changed from 2019-08-21 to 2020-08-21
- Checklist item changed from [x] totest-manager, [x] origin manager, [x] manager_42, [ ] build fail reminder, [x] staging-bot, [x] support packages rebuild, [x] pkglistgen, [x] trigger rebuild, [x] duplicate binaries, [x] openqa comments to [x] totest-manager, [x] origin manager, [x] manager_42, [ ] build fail reminder, [x] staging-bot, [x] support packages rebuild, [x] pkglistgen, [x] trigger rebuild, [x] duplicate binaries, [x] openqa comments, [ ] announcer
The announcer is missing in the checklist. Should we also run that in gocd now? any update wrt build fail reminder?
- Checklist item changed from [x] totest-manager, [x] origin manager, [x] manager_42, [ ] build fail reminder, [x] staging-bot, [x] support packages rebuild, [x] pkglistgen, [x] trigger rebuild, [x] duplicate binaries, [x] openqa comments, [ ] announcer to [x] totest-manager, [x] origin manager, [x] manager_42, [ ] build fail reminder, [x] staging-bot, [x] support packages rebuild, [x] pkglistgen, [x] trigger rebuild, [x] duplicate binaries, [x] openqa comments, [x] announcer
- Assignee changed from coolo to lnussel
the build fail reminder is set, but I paused the pipeline for you to trigger it when you feel it's needed (and check the config)
- Checklist item changed from to [x] build fail reminder
- % Done changed from 90 to 100
- Status changed from In Progress to Closed
Also available in: Atom
PDF