From 19859355a4d7db108f55376badd5c03d79b37f17 Mon Sep 17 00:00:00 2001 From: Ian Khor Date: Thu, 18 Jul 2024 04:55:06 +0000 Subject: [PATCH 1/5] Update file 18-0-deprecation-of-compliance-pipelines-and-migration-to-pipeline-execution-policy-types --- ...-and-migration-to-pipeline-execution-policy-types | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 data/deprecations/18-0-deprecation-of-compliance-pipelines-and-migration-to-pipeline-execution-policy-types diff --git a/data/deprecations/18-0-deprecation-of-compliance-pipelines-and-migration-to-pipeline-execution-policy-types b/data/deprecations/18-0-deprecation-of-compliance-pipelines-and-migration-to-pipeline-execution-policy-types new file mode 100644 index 00000000000000..41261eed064525 --- /dev/null +++ b/data/deprecations/18-0-deprecation-of-compliance-pipelines-and-migration-to-pipeline-execution-policy-types @@ -0,0 +1,12 @@ +- title: "Deprecation of Compliance Pipelines and Migration to Policy Execution Types" + removal_milestone: "18.0" + announcement_milestone: "17.9" + breaking_change: true + reporter: khornergit + stage: Govern + issue_url: https://gitlab.com/groups/gitlab-org/-/epics/11275 + body: | # (required) Don't change this line. + Compliance pipelines can be used to ensure specific compliance-related jobs are run on pipelines for all projects in a group. Currently, compliance pipelines are applied to projects through compliance frameworks. + Users want a single source for enforcing jobs to be run as part of a project pipeline. They want a way to combine the flexibility of compliance framework pipelines with the simplicity of scan execution policies. + + From GitLab 18.0, compliance pipelines will be deprecated in favour of using pipeline execution policy types, released in 17.3, instead. \ No newline at end of file -- GitLab From 08f3d16eec8a10838404c46460996f69768fa162 Mon Sep 17 00:00:00 2001 From: Ian Khor Date: Fri, 19 Jul 2024 03:53:28 +0000 Subject: [PATCH 2/5] Apply 1 suggestion(s) to 1 file(s) Co-authored-by: Evan Read --- ...e-pipelines-and-migration-to-pipeline-execution-policy-types | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/data/deprecations/18-0-deprecation-of-compliance-pipelines-and-migration-to-pipeline-execution-policy-types b/data/deprecations/18-0-deprecation-of-compliance-pipelines-and-migration-to-pipeline-execution-policy-types index 41261eed064525..5f60ae83aa1758 100644 --- a/data/deprecations/18-0-deprecation-of-compliance-pipelines-and-migration-to-pipeline-execution-policy-types +++ b/data/deprecations/18-0-deprecation-of-compliance-pipelines-and-migration-to-pipeline-execution-policy-types @@ -1,4 +1,4 @@ -- title: "Deprecation of Compliance Pipelines and Migration to Policy Execution Types" +- title: "Compliance pipelines" removal_milestone: "18.0" announcement_milestone: "17.9" breaking_change: true -- GitLab From 23c7345cf14a15338fc6432e9912f39b1dfb2be9 Mon Sep 17 00:00:00 2001 From: Evan Read Date: Mon, 22 Jul 2024 12:01:27 +1000 Subject: [PATCH 3/5] Edit deprecation and generate Markdown --- ...ion-to-pipeline-execution-policy-types.yml | 19 +++++++++++++++ ...gration-to-pipeline-execution-policy-types | 12 ---------- doc/update/deprecations.md | 24 +++++++++++++++++++ 3 files changed, 43 insertions(+), 12 deletions(-) create mode 100644 data/deprecations/17-3-deprecation-of-compliance-pipelines-and-migration-to-pipeline-execution-policy-types.yml delete mode 100644 data/deprecations/18-0-deprecation-of-compliance-pipelines-and-migration-to-pipeline-execution-policy-types diff --git a/data/deprecations/17-3-deprecation-of-compliance-pipelines-and-migration-to-pipeline-execution-policy-types.yml b/data/deprecations/17-3-deprecation-of-compliance-pipelines-and-migration-to-pipeline-execution-policy-types.yml new file mode 100644 index 00000000000000..19cc0eaf0393bd --- /dev/null +++ b/data/deprecations/17-3-deprecation-of-compliance-pipelines-and-migration-to-pipeline-execution-policy-types.yml @@ -0,0 +1,19 @@ +- title: "Compliance pipelines" + removal_milestone: "18.0" + announcement_milestone: "17.3" + breaking_change: true + reporter: khornergit + stage: Govern + issue_url: https://gitlab.com/groups/gitlab-org/-/epics/11275 + body: | + Currently, there are two ways to ensure compliance- or security-related jobs are run in a project pipeline: + + - [Compliance pipelines](https://docs.gitlab.com/ee/user/group/compliance_pipelines.html). + - [Scan execution policies](https://docs.gitlab.com/ee/user/application_security/policies/scan-execution-policies.html). + + To provide a single place for ensuing required jobs are run in all pipelines for a project, we have deprecated + compliance pipelines GitLab 17.3 and will remove the feature in GitLab 18.0. + + Customers should migrate from compliance pipelines to the new + [pipeline execution policy type](https://docs.gitlab.com/ee/user/application_security/policies/pipeline_execution_policies.html) + as soon as possible. diff --git a/data/deprecations/18-0-deprecation-of-compliance-pipelines-and-migration-to-pipeline-execution-policy-types b/data/deprecations/18-0-deprecation-of-compliance-pipelines-and-migration-to-pipeline-execution-policy-types deleted file mode 100644 index 5f60ae83aa1758..00000000000000 --- a/data/deprecations/18-0-deprecation-of-compliance-pipelines-and-migration-to-pipeline-execution-policy-types +++ /dev/null @@ -1,12 +0,0 @@ -- title: "Compliance pipelines" - removal_milestone: "18.0" - announcement_milestone: "17.9" - breaking_change: true - reporter: khornergit - stage: Govern - issue_url: https://gitlab.com/groups/gitlab-org/-/epics/11275 - body: | # (required) Don't change this line. - Compliance pipelines can be used to ensure specific compliance-related jobs are run on pipelines for all projects in a group. Currently, compliance pipelines are applied to projects through compliance frameworks. - Users want a single source for enforcing jobs to be run as part of a project pipeline. They want a way to combine the flexibility of compliance framework pipelines with the simplicity of scan execution policies. - - From GitLab 18.0, compliance pipelines will be deprecated in favour of using pipeline execution policy types, released in 17.3, instead. \ No newline at end of file diff --git a/doc/update/deprecations.md b/doc/update/deprecations.md index d9db452ec9117f..194e9a3220454a 100644 --- a/doc/update/deprecations.md +++ b/doc/update/deprecations.md @@ -158,6 +158,30 @@ The change will be introduced in GitLab 16.6 behind a feature flag. If you are i
+### Compliance pipelines + +
+- Announced in GitLab 17.3 +- Removal in GitLab 18.0 ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change)) +- To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/groups/gitlab-org/-/epics/11275). +
+ +Currently, there are two ways to ensure compliance- or security-related jobs are run in a project pipeline: + +- [Compliance pipelines](https://docs.gitlab.com/ee/user/group/compliance_pipelines.html). +- [Scan execution policies](https://docs.gitlab.com/ee/user/application_security/policies/scan-execution-policies.html). + +To provide a single place for ensuing required jobs are run in all pipelines for a project, we have deprecated +compliance pipelines GitLab 17.3 and will remove the feature in GitLab 18.0. + +Customers should migrate from compliance pipelines to the new +[pipeline execution policy type](https://docs.gitlab.com/ee/user/application_security/policies/pipeline_execution_policies.html) +as soon as possible. + +
+ +
+ ### Default CI/CD job token (`CI_JOB_TOKEN`) scope changed
-- GitLab From 8fbbb1f6501400a32b681d7ee5807520afcb94cd Mon Sep 17 00:00:00 2001 From: Ian Khor Date: Thu, 25 Jul 2024 02:38:39 +0000 Subject: [PATCH 4/5] Apply 1 suggestion(s) to 1 file(s) Co-authored-by: Nate Rosandich --- ...pelines-and-migration-to-pipeline-execution-policy-types.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/data/deprecations/17-3-deprecation-of-compliance-pipelines-and-migration-to-pipeline-execution-policy-types.yml b/data/deprecations/17-3-deprecation-of-compliance-pipelines-and-migration-to-pipeline-execution-policy-types.yml index 19cc0eaf0393bd..6b609b06787d97 100644 --- a/data/deprecations/17-3-deprecation-of-compliance-pipelines-and-migration-to-pipeline-execution-policy-types.yml +++ b/data/deprecations/17-3-deprecation-of-compliance-pipelines-and-migration-to-pipeline-execution-policy-types.yml @@ -9,7 +9,7 @@ Currently, there are two ways to ensure compliance- or security-related jobs are run in a project pipeline: - [Compliance pipelines](https://docs.gitlab.com/ee/user/group/compliance_pipelines.html). - - [Scan execution policies](https://docs.gitlab.com/ee/user/application_security/policies/scan-execution-policies.html). + - [Security policies](https://docs.gitlab.com/ee/user/application_security/policies/). To provide a single place for ensuing required jobs are run in all pipelines for a project, we have deprecated compliance pipelines GitLab 17.3 and will remove the feature in GitLab 18.0. -- GitLab From c0295fa109bc2aadf9fe210fed28f304f8cfcca1 Mon Sep 17 00:00:00 2001 From: nrosandich Date: Mon, 29 Jul 2024 11:40:01 +1200 Subject: [PATCH 5/5] Update generated markdown --- doc/update/deprecations.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/update/deprecations.md b/doc/update/deprecations.md index 194e9a3220454a..b8f3730b0b4835 100644 --- a/doc/update/deprecations.md +++ b/doc/update/deprecations.md @@ -169,7 +169,7 @@ The change will be introduced in GitLab 16.6 behind a feature flag. If you are i Currently, there are two ways to ensure compliance- or security-related jobs are run in a project pipeline: - [Compliance pipelines](https://docs.gitlab.com/ee/user/group/compliance_pipelines.html). -- [Scan execution policies](https://docs.gitlab.com/ee/user/application_security/policies/scan-execution-policies.html). +- [Security policies](https://docs.gitlab.com/ee/user/application_security/policies/). To provide a single place for ensuing required jobs are run in all pipelines for a project, we have deprecated compliance pipelines GitLab 17.3 and will remove the feature in GitLab 18.0. -- GitLab