Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- # This script adds some automatisms helping to manage the integration queues:
- # - candidates queue: issues awaiting from integration not yet in current.
- # - current queue: issues under current integration.
- #
- # The automatisms are as follow:
- # A) Move "important" issues from candidates to current.
- # B) Keep the current queue fed with issues from the candidates queue in rigorous priority order.
- # - When the number of issues awaiting for integration falls below a threshold (currentmin).
- # - Moving up to a maximum number of issue (movemax).
- # C) There isn't any C, the above are all (way simpler than the continuous queues manager).
- # The criteria to consider an issue "important" are:
- # 1) It must be in the candidates queue, awaiting for integration. |
- # 2) It must not have the integration_held or security_held labels. | => filter=14000
- # 3) It must not have the "agreed_to_be_after_release" text in a comment.| => NOT filter = 21366
- # 4) At least one of this is true:
- # a) The issue has a must-fix version. | => filter = 21363
- # b) The issue has the mdlqa label. | => labels IN (mdlqa)
- # c) The issue priority is critical or higher. | => priority IN (Critical, Blocker)
- # d) The issue is flagged as security issue. | => level IS NOT EMPTY
- # e) The issue belongs to some of these components: | => component IN (...)
- # - Privacy
- # - Automated functional tests (behat)
- # - Unit tests
- #
- # This job must be enabled over normal weeklies period (since end of on-sync to freeze).
Add Comment
Please, Sign In to add comment