Update cluster management project template to latest revision
What does this MR do and why?
Describe in detail what your merge request does and why.
This change set updates the cluster_management project template to (most importantly) include Move to no-dind renovate template and pin it (gitlab-org/project-templates/cluster-management!70 - merged).
I've used the following command to update the archive:
bundle exec rake gitlab:update_project_templates\[cluster_management\]
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Merge request reports
Activity
assigned to @timofurrer
/cc @DarwinJS
changed milestone to %16.0
added bugfunctional groupenvironments workflowready for review labels
requested review from @tigerwnz
added typebug label
added devopsdeploy sectionops labels
mentioned in issue gitlab-org/project-templates/cluster-management#48 (closed)
- A deleted user
added backend label
1 Message CHANGELOG missing: If you want to create a changelog entry for GitLab FOSS, add the
Changelog
trailer to the commit message you want to add to the changelog.If you want to create a changelog entry for GitLab EE, also add the
EE: true
trailer to your commit message.If this merge request doesn't need a CHANGELOG entry, feel free to ignore this message.
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 Eugenia Grieff (
@egrieff
) (UTC+2, same timezone as@timofurrer
)Tetiana Chupryna (
@brytannia
) (UTC+2, same timezone as@timofurrer
)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 Tetiana Chupryna
Sorry @timofurrer, I didn't think this through enough
I've just merged gitlab-org/project-templates/cluster-management!71 (merged), which will also require an update. Shall we do them both at the same time?
added 999 commits
-
d9abaee2...e329222b - 998 commits from branch
master
- a452731c - Update cluster management project template to latest revision
-
d9abaee2...e329222b - 998 commits from branch
marked the checklist item I have evaluated the MR acceptance checklist for this MR. as completed
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 Sylvester Chin (
@schin1
) (UTC+8, 6 hours ahead of@timofurrer
)James Fargher (
@proglottis
) (UTC+12, 10 hours ahead of@timofurrer
)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
Dangerrequested review from @brytannia and removed review request for @tigerwnz
@tigerwnz
, thanks for approving this merge request.This is the first time the merge request is approved. To ensure full test coverage, a new pipeline will be started shortly.
For more info, please refer to the following links:
added pipeline:mr-approved label
mentioned in commit 00e8f234
added 45 commits
-
a452731c...5c105563 - 44 commits from branch
master
- 00e8f234 - Update cluster management project template to latest revision
-
a452731c...5c105563 - 44 commits from branch
mentioned in issue #352399 (closed)
enabled an automatic merge when the pipeline for 0fff3853 succeeds
mentioned in commit d3753e58
added workflowstaging-canary label and removed workflowready for review label
@timofurrer - thanks for doing this!
This process is way too non-automated and slow given the fact that the customer experience of the quality of this code is primarily through the projects that are used as the project templates. It would be very prudent to get this last mile completely automated - I'm looking forward to that!
Thanks again.
@DarwinJS yes, I totally agree.
For anyone following here, there is Change project templates contribution flow (#384005)
Edited by Timo Furrer
added workflowcanary label and removed workflowstaging-canary label
added workflowstaging label and removed workflowcanary label
added workflowproduction label and removed workflowstaging label
added workflowpost-deploy-db-staging label and removed workflowproduction label
added workflowpost-deploy-db-production label and removed workflowpost-deploy-db-staging label
added releasedcandidate label
mentioned in merge request kubitus-project/kubitus-installer!2145 (merged)