Use latest builder images for check-packages pipeline
What does this MR do?
Use latest builder images for check-packages pipeline. It prevents issues like upstream repos changing their cryptographic signatures which are not present in older images, but are present in the latest ones.
While using a floating tag like latest
is generally a bad design decision, here the steps performed are basic (a curl command and an apt/yum/zypper install command) and not depending on any of the runtime versions, it should hopefully fine.
Related issues
Closes #8645 (closed)
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 "~workflow::ready 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. -
If config/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 the Trigger: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.
Expected (please provide an explanation if not completing)
-
Test plan indicating conditions for success has been posted and passes. -
Documentation created/updated. -
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 integer 10
, 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.3
assigned to @balasankarc
removed For Scheduling label
Reviewer 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-5, 10.5 hours behind
@balasankarc
)@rmarshall
(UTC-4, 9.5 hours behind
@balasankarc
)If needed, you can retry the
danger-review
job that generated this comment.Generated by
Danger@axugl Could you take a look and pass on to Andrew for review/merge? Thanks.
requested review from @axugl
mentioned in issue #8658 (closed)
marked the checklist item When ready for review, MR is labeled "~workflow::ready for review" per the Distribution MR workflow. as completed
added workflowin review label
E2E Test Result Summary
allure-report-publisher
generated test report!qa-subset-test:
test report for 7f88eae1expand test summary
+---------------------------------------------------------------------+ | suites summary | +----------------+--------+--------+---------+-------+-------+--------+ | | passed | failed | skipped | flaky | total | result | +----------------+--------+--------+---------+-------+-------+--------+ | Govern | 47 | 0 | 1 | 0 | 48 | ✅ | | Systems | 7 | 0 | 0 | 0 | 7 | ✅ | | Plan | 19 | 0 | 0 | 0 | 19 | ✅ | | GitLab Metrics | 2 | 0 | 1 | 0 | 3 | ✅ | | Create | 69 | 0 | 9 | 0 | 78 | ✅ | | Data Stores | 11 | 0 | 0 | 0 | 11 | ✅ | | Monitor | 8 | 0 | 1 | 0 | 9 | ✅ | | Package | 10 | 0 | 4 | 0 | 14 | ✅ | | Verify | 4 | 0 | 1 | 0 | 5 | ✅ | | Configure | 1 | 0 | 0 | 0 | 1 | ✅ | | Release | 1 | 0 | 0 | 0 | 1 | ✅ | | Manage | 2 | 0 | 0 | 0 | 2 | ✅ | +----------------+--------+--------+---------+-------+-------+--------+ | Total | 181 | 0 | 17 | 0 | 198 | ✅ | +----------------+--------+--------+---------+-------+-------+--------+
mentioned in issue gitlab-com/gl-infra/delivery#20420 (closed)
- Simulated a tagged release
- Examined output at dev gitlab
Using Docker executor with image registry.gitlab.com/gitlab-org/gitlab-omnibus-builder/debian_12:latest ...
LGTM
Edited by Alec Xurequested review from @apatterson2
marked the checklist item If CI configuration is changed, the branch must be pushed to
dev.gitlab.org
to confirm regular branch builds aren't broken. as completedmentioned in commit b96ab26e
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
added releasedcandidate label
added releasedpublished label and removed releasedcandidate label
mentioned in merge request !7876 (merged)
mentioned in merge request !7877 (merged)
mentioned in merge request release-tools!3413 (closed)
mentioned in merge request release-tools!3405 (closed)
mentioned in merge request !7878 (merged)
mentioned in merge request !7879 (merged)
mentioned in incident gitlab-com/gl-infra/production#18621 (closed)
mentioned in merge request !7975 (merged)
mentioned in merge request !7976 (merged)
mentioned in merge request !7977 (merged)
mentioned in merge request !7978 (merged)
mentioned in merge request !7979 (merged)
mentioned in merge request !7980 (merged)
mentioned in merge request !7981 (merged)
mentioned in merge request !7982 (merged)
mentioned in merge request !7983 (merged)
mentioned in merge request !7984 (merged)
mentioned in merge request !7985 (merged)
mentioned in issue #8766 (closed)