Stop building OpenSUSE Leap 15.5 packages
What does this MR do?
Stop building OpenSUSE Leap 15.5 packages
OpenSUSE Leap 15.5 went EOL in December 2025 and was announced to be removed in GitLab 17.9.
Relates #8778 (closed)
Changelog: removed
Related issues
Checklist
See Definition of done.
For anything in this list which will not be completed, please provide a reason in the MR discussion.
Required
-
MR title and description are up to date, accurate, and descriptive. -
MR targeting the appropriate branch. -
Latest Merge Result pipeline is green. -
When ready for review, MR is labeled workflowready for review per the Distribution MR workflow.
For GitLab team members
If you don't have access to this, the reviewer should trigger these jobs for you during the review process.
-
The manual Trigger:ee-package
jobs have a green pipeline running against latest commit. -
Ifconfig/software
orconfig/patches
directories are changed, make sure thebuild-package-on-all-os
job within theTrigger:ee-package
downstream pipeline succeeded. -
If you are changing anything SSL related, then theTrigger:package:fips
manual job within theTrigger:ee-package
downstream pipeline must succeed. -
If CI configuration is changed, the branch must be pushed to dev.gitlab.org
to confirm regular branch builds aren't broken. https://dev.gitlab.org/gitlab/omnibus-gitlab/-/pipelines/360922
Expected (please provide an explanation if not completing)
-
Test plan indicating conditions for success has been posted and passes. -
Documentation created/updated. gitlab!177873 (merged) -
Tests added. -
Integration tests added to GitLab QA. -
Equivalent MR/issue for the GitLab Chart opened. -
Validate potential values for new configuration settings. Formats such as integer10
, duration10s
, URIscheme://user:passwd@host:port
may require quotation or other special handling when rendered in a template and written to a configuration file.
Merge request reports
Activity
changed milestone to %17.9
assigned to @clemensbeck
marked the checklist item When ready for review, MR is labeled workflowready for review per the Distribution MR workflow. as completed
1 Message Once your MR is ready for review you can comment @gitlab-bot ready <@user>
to request the first review to someone. It's recommended that you pick the one suggested by the reviewer roulette. But you can ignore it and assign it to someone else if you see fit.Merge requests are handled according to the workflow documented in our handbook and should receive a response within the limit documented in our Service-level objective (SLO).
If you don't receive a response from the reviewer within the SLO, please mention
@gitlab-org/distribution
, or one of our Project MaintainersReviewer roulette
Changes that require review have been detected! A merge request is normally reviewed by both a reviewer and a maintainer in its primary category and by a maintainer in all other categories.
To spread load more evenly across eligible reviewers, Danger has picked a candidate for each review slot. Feel free to override these selections if you think someone else would be better-suited or use the GitLab Review Workload Dashboard to find other available reviewers.
To read more on how to use the reviewer roulette, please take a look at the Engineering workflow and code review guidelines. Please consider assigning a reviewer or maintainer who is a domain expert in the area of the merge request.
Once you've decided who will review this merge request, mention them as you normally would! Danger does not automatically notify them for you.
Reviewer Maintainer @dustinmm80
(UTC-6, 7 hours behind
@clemensbeck
)@ibaum
(UTC-6, 7 hours behind
@clemensbeck
)If needed, you can retry the
danger-review
job that generated this comment.Generated by
Dangermentioned in issue #8778 (closed)
@dustinmm80 Can you please review? Note: The MR is configured to not merge before 2025-01-17 because this must not land in 17.8 stable branch.
added workflowready for review label
requested review from @dustinmm80
E2E Test Result Summary
allure-report-publisher
generated test report!qa-subset-test:
test report for dc5660b4expand test summary
+----------------------------------------------------------------+ | suites summary | +-----------+--------+--------+---------+-------+-------+--------+ | | passed | failed | skipped | flaky | total | result | +-----------+--------+--------+---------+-------+-------+--------+ | Systems | 6 | 0 | 1 | 0 | 7 | ✅ | | Govern | 24 | 0 | 1 | 0 | 25 | ✅ | | Plan | 1 | 0 | 0 | 0 | 1 | ✅ | | Package | 7 | 0 | 0 | 0 | 7 | ✅ | | Monitor | 4 | 0 | 1 | 0 | 5 | ✅ | | Manage | 2 | 0 | 0 | 0 | 2 | ✅ | | Configure | 1 | 0 | 0 | 0 | 1 | ✅ | +-----------+--------+--------+---------+-------+-------+--------+ | Total | 45 | 0 | 3 | 0 | 48 | ✅ | +-----------+--------+--------+---------+-------+-------+--------+
added workflowin review label and removed workflowready for review label
All looks good here. All references to 15.5 have been removed in code, full triggered pipeline is green. Inspecting pipeline https://gitlab.com/gitlab-org/omnibus-gitlab/-/pipelines/1624341653 no 15.5 jobs are present. Approving MR and passing to @ibaum for maintainer review.
requested review from @ibaum
enabled an automatic merge when all merge checks for dc5660b4 pass
This looks good to me @clemensbeck! I've set to auto merge.
mentioned in merge request gitlab-omnibus-builder!370 (merged)
mentioned in commit d8bfc8b5
added workflowstaging-canary label and removed workflowin review label
added workflowcanary label and removed workflowstaging-canary label
added workflowstaging label and removed workflowcanary label
added workflowproduction label and removed workflowstaging label
mentioned in merge request !8121 (merged)
added releasedcandidate label
added releasedpublished label and removed releasedcandidate label