-
Notifications
You must be signed in to change notification settings - Fork 724
Backport #11213: gitlab ci: Use today's ci-images build; move to alpine3_22 #11320
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
Conversation
Merge Queue Status🚫 The pull request has left the queue (rule: This pull request spent 1 hour 40 minutes 2 seconds in the queue, including 1 hour 29 minutes 28 seconds running CI. Required conditions to merge
ReasonThe merge conditions cannot be satisfied due to failing checks Failing checks: HintYou may have to fix your CI before adding the pull request to the queue again. |
|
@mergify rebase |
(cherry picked from commit e063b3e)
725b1a9 to
cda59f6
Compare
☑️ Nothing to do, the required conditions are not met
|
Merge Queue Status✅ The pull request has been merged This pull request spent 11 minutes 5 seconds in the queue, with no time running CI. Required conditions to merge
|
Background: Release CI has been implemented on GitHub, but my working assumption is that the previous GitLab CI will still be used for minor releases of 3.16 to ensure no breaking changes regarding platform availability.
Situation: GitLab CI (may it soon RIP) is failing and will take a hot minute to fix again
Possible solutions
Option 1: Declare GitLab bankruptcy and give up. Go whole-hog on the new GitHub CI, platform availability be damned.
Option 2: Accept some minor change in platform availability. The list would be:
Pipeline example:
Option 3: Something else that I realistically don't have time for and probably nobody else does, either.
This PR implements option 2. If merged, it should be backported to the 3.16 branch.
This is an automatic backport of pull request #11213 done by Mergify.