Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[8.16] buildkite(dra): retry if package failed (backport #14783) #14789

Merged
merged 1 commit into from
Dec 3, 2024

buildkite(dra): retry if package failed (#14783)

fef1c63
Select commit
Loading
Failed to load commit list.
Merged

[8.16] buildkite(dra): retry if package failed (backport #14783) #14789

buildkite(dra): retry if package failed (#14783)
fef1c63
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Dec 9, 2024 in 0s

5 potential rules

Rule: ask to resolve conflict (comment)

  • conflict

Rule: remove backport-skip label (label)

  • label~=^backport-\d

Rule: remove backport-8.x label if backport-skip is present (label)

  • label~=^backport-skip

Rule: notify the backport has not been merged yet (comment)

  • -closed
  • -merged
  • schedule=Mon-Mon 06:00-10:00[Europe/Paris]
  • #check-success>0
  • author=mergify[bot]

Rule: squash and merge backport PRs after CI passes (queue)

  • -closed [📌 queue requirement]
  • -conflict
  • -conflict [📌 queue requirement]
  • -draft [📌 queue requirement]
  • author=mergify[bot]
  • label=backport
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [🔀 queue conditions]
    • all of: [📌 queue conditions of queue default]
      • #approved-reviews-by >= 1 [🛡 GitHub branch protection]
      • #approved-reviews-by >= 1 [🛡 GitHub repository ruleset rule]
      • #approved-reviews-by >= 1 [🛡 GitHub repository ruleset rule]
      • #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
      • #changes-requested-reviews-by = 0 [🛡 GitHub repository ruleset rule]
      • #changes-requested-reviews-by = 0 [🛡 GitHub repository ruleset rule]
      • any of: [🛡 GitHub branch protection]
        • check-success = CLA
        • check-neutral = CLA
        • check-skipped = CLA
      • any of: [🛡 GitHub branch protection]
        • check-success = lint
        • check-neutral = lint
        • check-skipped = lint
      • any of: [🛡 GitHub branch protection]
        • check-success = buildkite/docs-build-pr
        • check-neutral = buildkite/docs-build-pr
        • check-skipped = buildkite/docs-build-pr

💖  Mergify is proud to provide this service for free to open source projects.

🚀  You can help us by becoming a sponsor!


28 not applicable rules

Rule: squash and merge updatecli PRs after CI passes (queue)

  • -closed [📌 queue requirement]
  • head~=^updatecli
  • label=automation
  • -conflict
  • -conflict [📌 queue requirement]
  • -draft [📌 queue requirement]
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [🔀 queue conditions]
    • all of: [📌 queue conditions of queue default]
      • #approved-reviews-by >= 1 [🛡 GitHub branch protection]
      • #approved-reviews-by >= 1 [🛡 GitHub repository ruleset rule]
      • #approved-reviews-by >= 1 [🛡 GitHub repository ruleset rule]
      • #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
      • #changes-requested-reviews-by = 0 [🛡 GitHub repository ruleset rule]
      • #changes-requested-reviews-by = 0 [🛡 GitHub repository ruleset rule]
      • any of: [🛡 GitHub branch protection]
        • check-success = CLA
        • check-neutral = CLA
        • check-skipped = CLA
      • any of: [🛡 GitHub branch protection]
        • check-success = lint
        • check-neutral = lint
        • check-skipped = lint
      • any of: [🛡 GitHub branch protection]
        • check-success = buildkite/docs-build-pr
        • check-neutral = buildkite/docs-build-pr
        • check-skipped = buildkite/docs-build-pr

Rule: delete updatecli branch after merging/closing it (delete_head_branch)

  • all of:
    • head~=^updatecli
    • label=automation
  • closed [📌 delete_head_branch requirement]
  • any of:
    • closed
    • merged

Rule: backport patches to 8.4 branch (backport)

  • base=main
  • label=backport-8.4
  • merged
  • merged [📌 backport requirement]

Rule: backport patches to 8.3 branch (backport)

  • base=main
  • label=backport-8.3
  • merged
  • merged [📌 backport requirement]

Rule: backport patches to 8.2 branch (backport)

  • base=main
  • label=backport-8.2
  • merged
  • merged [📌 backport requirement]

Rule: backport patches to 8.1 branch (backport)

  • base=main
  • label=backport-8.1
  • merged
  • merged [📌 backport requirement]

Rule: backport patches to 8.0 branch (backport)

  • base=main
  • label=backport-8.0
  • merged
  • merged [📌 backport requirement]

Rule: backport patches to 7.17 branch (backport)

  • base=main
  • label=backport-7.17
  • merged
  • merged [📌 backport requirement]

Rule: backport patches to 7.16 branch (backport)

  • base=main
  • label=backport-7.16
  • merged
  • merged [📌 backport requirement]

Rule: backport patches to 7.15 branch (backport)

  • base=main
  • label=backport-7.15
  • merged
  • merged [📌 backport requirement]

Rule: backport patches to 7.14 branch (backport)

  • base=main
  • label=backport-7.14
  • merged
  • merged [📌 backport requirement]

Rule: backport patches to 7.13 branch (backport)

  • base=main
  • label=backport-7.13
  • merged
  • merged [📌 backport requirement]

Rule: notify the backport policy (comment)

  • -label~=^backport
  • base=main

Rule: add backport-8.x for the all the PRs targeting main if no skipped or assigned already (comment, label)

  • base=main
  • -label~=^(backport-skip|backport-8.x)$

Rule: backport patches to 8.5 branch (backport)

  • base=main
  • label=backport-8.5
  • merged
  • merged [📌 backport requirement]

Rule: backport patches to 8.6 branch (backport)

  • base=main
  • label=backport-8.6
  • merged
  • merged [📌 backport requirement]

Rule: backport patches to 8.7 branch (backport)

  • base=main
  • label=backport-8.7
  • merged
  • merged [📌 backport requirement]

Rule: backport patches to 8.8 branch (backport)

  • base=main
  • label=backport-8.8
  • merged
  • merged [📌 backport requirement]

Rule: backport patches to 8.9 branch (backport)

  • base=main
  • label=backport-8.9
  • merged
  • merged [📌 backport requirement]

Rule: backport patches to 8.10 branch (backport)

  • base=main
  • label=backport-8.10
  • merged
  • merged [📌 backport requirement]

Rule: backport patches to 8.11 branch (backport)

  • base=main
  • label=backport-8.11
  • merged
  • merged [📌 backport requirement]

Rule: backport patches to 8.12 branch (backport)

  • base=main
  • label=backport-8.12
  • merged
  • merged [📌 backport requirement]

Rule: backport patches to 8.13 branch (backport)

  • base=main
  • label=backport-8.13
  • merged
  • merged [📌 backport requirement]

Rule: backport patches to 8.14 branch (backport)

  • base=main
  • label=backport-8.14
  • merged
  • merged [📌 backport requirement]

Rule: backport patches to 8.15 branch (backport)

  • base=main
  • label=backport-8.15
  • merged
  • merged [📌 backport requirement]

Rule: backport patches to 8.x branch (backport)

  • base=main
  • label=backport-8.x
  • merged
  • merged [📌 backport requirement]

Rule: backport patches to 8.16 branch (backport)

  • base=main
  • label=backport-8.16
  • merged
  • merged [📌 backport requirement]

Rule: backport patches to 8.17 branch (backport)

  • base=main
  • label=backport-8.17
  • merged
  • merged [📌 backport requirement]
Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the rules
  • @Mergifyio rebase will rebase this PR on its base branch
  • @Mergifyio update will merge the base branch into this PR
  • @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com