Update GitLab Runner Helm Chart to 0.31.0/14.1.0
What does this MR do?
Update's used GitLab Runner Helm Chart to version 0.31.0 which uses GitLab Runner 14.1.0.
What are the relevant issue numbers?
Does this MR meet the acceptance criteria?
-
Changelog entry added, if necessary -
Documentation created/updated via this MR -
Documentation reviewed by technical writer or follow-up review issue created -
Tests added for this feature/bug -
Tested in all supported browsers -
Conforms to the code review guidelines -
Conforms to the merge request performance guidelines -
Conforms to the style guides -
Conforms to the database guides -
Link to e2e tests MR added if this MR has Requires e2e tests label. See the Test Planning Process. -
Security reports checked/validated by reviewer
Merge request reports
Activity
changed milestone to %14.2
mentioned in issue gitlab-runner#28046 (closed)
- A deleted user
added backend label
1 Warning You've made some app changes, but didn't add any tests.
That's OK as long as you're refactoring existing code,
but please consider adding any of the tooling, ~"tooling::pipelines", ~"tooling::workflow", documentation, QA labels.Reviewer roulette
Changes that require review have been detected!
Please refer to the table below for assigning reviewers and maintainers suggested by Danger in the specified category:
Category Reviewer Maintainer backend Vasilii Iakliushin ( @vyaklushin
) (UTC+2, same timezone as@steveazz
)Douglas Barbosa Alexandre ( @dbalexandre
) (UTC-3, 5 hours behind@steveazz
)To spread load more evenly across eligible reviewers, Danger has picked a candidate for each review slot, based on their timezone. 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, assign them as a reviewer! Danger does not automatically notify them for you.
If needed, you can retry the
danger-review
job that generated this comment.Generated by
Danger- Resolved by Douglas Barbosa Alexandre
@vyaklushin would you be so kind to review this?
requested review from @vyaklushin
requested review from @dbalexandre and removed review request for @vyaklushin
- Resolved by Douglas Barbosa Alexandre
@vyaklushin, thanks for approving this merge request.Please consider starting a new pipeline if:
- This is the first time the merge request is approved, or
- The merge request is ready to be merged, and there has not been a merge request pipeline in the last 2 hours.
For more info, refer to the guideline.
- Resolved by Steve Xuereb - Out of Office Back 2025-04-21
@dbalexandre, thanks for approving this merge request.Please consider starting a new pipeline if:
- This is the first time the merge request is approved, or
- The merge request is ready to be merged, and there has not been a merge request pipeline in the last 2 hours.
For more info, refer to the guideline.
- Resolved by Douglas Barbosa Alexandre
Thanks, @steveazz! LGTM
enabled an automatic merge when the pipeline for 46913776 succeeds
mentioned in commit 36eddb8a
added workflowstaging label
added workflowcanary label and removed workflowstaging label
added workflowproduction label and removed workflowcanary label
added releasedcandidate label
added releasedpublished label and removed releasedcandidate label
mentioned in merge request kubitus-project/kubitus-installer!123 (merged)