-
Lee Tickett authored
- Assign the author to the merge request as part of the template configuration.
Lee Tickett authored- Assign the author to the merge request as part of the template configuration.
Component upgrade.md 2.96 KiB
What does this MR do?
%{first_multiline_commit}
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 targets the appropriate branch.
- Component test plan copied into MR description.
- Latest merged results 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 permissions to trigger pipelines for this MR, 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. To debug QA failures, refer to Investigate QA failures. -
If
config/software
orconfig/patches
directories are changed,build-package-on-all-os
job within theTrigger:ee-package
downstream pipeline succeeded. -
If you are changing anything SSL related, the
Trigger:package:fips
manual job within theTrigger:ee-package
downstream pipeline succeeded. -
If CI/CD configuration is changed, the branch is 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 or updated.
- Tests added.
- Integration tests added to GitLab QA.
- Equivalent MR/issue for the GitLab Chart opened.
-
Potential values for new configuration settings validated. 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.
Test plan
/assign me