When a change is swatted and the swatter comments SWAT this change should priortize over any other queued.
Description
Description
Related Objects
Related Objects
- Mentioned Here
- T160668: Create "High Priority" gate-and-submit pipeline
Event Timeline
Comment Actions
I disagree, we should do this via branches & repos: wmf/* branches should be prioritized, wmf-config and puppet should be prioritized.
(like we already started doing)
Comment Actions
@demon I will do that but i will still keep this idea floating about and see what others say
Comment Actions
What if I put SWAT in a lot of my comments just to prioritize my commits? ;-)
Again: this is a bad idea.
Comment Actions
@demon it would also look only in repos that are supposed to be swatted and only allow people with production access to trigger this
Comment Actions
The underlying problem is to have MediaWiki patches for Wikimedia to be prioritized or at least in a different queue than the random patches against master branches.
The proposal of using a comment SWAT similar to recheck is potentially a good idea, but can not be implemented with the CI system we use (namely Zuul).
So that is essentially a duplicate of T160668 which is to create a different queue and for which I have yet to come up with a solution.