diff options
author | GitLab Bot <gitlab-bot@gitlab.com> | 2023-02-10 06:10:56 +0000 |
---|---|---|
committer | GitLab Bot <gitlab-bot@gitlab.com> | 2023-02-10 06:10:56 +0000 |
commit | 36ff95a8a93225f47a833989429cc766a6ff2661 (patch) | |
tree | 2101cffff43469c06d846fcd1ed6a58acd06f735 /data/deprecations/15-9-required-pipeline-configuration.yml | |
parent | 677227413ae31f5a02fd4c8e10f6ef50c228334f (diff) | |
download | gitlab-ce-36ff95a8a93225f47a833989429cc766a6ff2661.tar.gz |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'data/deprecations/15-9-required-pipeline-configuration.yml')
-rw-r--r-- | data/deprecations/15-9-required-pipeline-configuration.yml | 28 |
1 files changed, 28 insertions, 0 deletions
diff --git a/data/deprecations/15-9-required-pipeline-configuration.yml b/data/deprecations/15-9-required-pipeline-configuration.yml new file mode 100644 index 00000000000..625d00cb07e --- /dev/null +++ b/data/deprecations/15-9-required-pipeline-configuration.yml @@ -0,0 +1,28 @@ +# +# REQUIRED FIELDS +# +- title: "Required Pipeline Configuration is deprecated" # (required) Clearly explain the change, or planned change. For example, "The `confidential` field for a `Note` is deprecated" or "CI/CD job names will be limited to 250 characters." + announcement_milestone: "15.9" # (required) The milestone when this feature was first announced as deprecated. + removal_milestone: "16.0" # (required) The milestone when this feature is planned to be removed + breaking_change: true # (required) Change to false if this is not a breaking change. + reporter: jheimbuck_gl # (required) GitLab username of the person reporting the change + stage: Verify # (required) String value of the stage that the feature was created in. e.g., Growth + issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/389467 # (required) Link to the deprecation issue in GitLab + body: | # (required) Do not modify this line, instead modify the lines below. + Required Pipeline Configuration will be removed in the 16.0 release. This impacts Self-Managed users on the Ultimate license. + + We recommend replacing this with an alternative [compliance solution](https://docs.gitlab.com/ee/user/group/compliance_frameworks.html#configure-a-compliance-pipeline) that is available now. We recommend this alternative solution because it provides greater flexibility, allowing required pipelines to be assigned to specific compliance framework labels. +# +# OPTIONAL END OF SUPPORT FIELDS +# +# If an End of Support period applies, the announcement should be shared with GitLab Support +# in the `#spt_managers` channel in Slack, and mention `@gitlab-com/support` in this MR. +# + end_of_support_milestone: # (optional) Use "XX.YY" format. The milestone when support for this feature will end. + # + # OTHER OPTIONAL FIELDS + # + tiers: # (optional - may be required in the future) An array of tiers that the feature is available in currently. e.g., [Free, Silver, Gold, Core, Premium, Ultimate] + documentation_url: https://docs.gitlab.com/ee/user/admin_area/settings/continuous_integration.html#required-pipeline-configuration # (optional) This is a link to the current documentation page + image_url: # (optional) This is a link to a thumbnail image depicting the feature + video_url: # (optional) Use the youtube thumbnail URL with the structure of https://img.youtube.com/vi/UNIQUEID/hqdefault.jpg |