deploy-promote should not allow promoting to group1 unless group0 is already in wikiversions.json. Similarly for the other groups.
Description
Description
Related Objects
Related Objects
- Mentioned In
- T263186: 1.36.0-wmf.20 deployment blockers
Event Timeline
Comment Actions
What I did this week was:
| Tuesday | deploy-promote testwikis |
| Wednesday | deploy-promote group1 |
Essentially skipping group0 since my mind was stuck to only have to run deploy-promote once per day. That is no more the case on Tuesday.
Comment Actions
This open task is only tagged with the RelEng Q2 project tag which recently has been archived. Please add an active project tag to this task so this task is discoverable. Thanks!
Comment Actions
I think using scap train makes it hard/impossible to do this. If you do use scap train to advance from (for example) group0 to group2, group1 will be promoted too.
Comment Actions
I clearly remember having skip a group (T269242#6667203) which was four years ago and probably the sole time I did. The scap train commands has a human friendly text UI which makes it easy to see at which stage were are. We also have https://versions.toolforge.org/ !