Skip to content

Compliance Pipeline to Security Policy Migration - Feedback issue

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

What is happening

groupcompliance are planning on deprecating compliance pipelines from the 17.3 release onwards and remove it completely as a breaking change as part of the 18.0 release. We will be asking customers to use pipeline execution policy types instead moving forward.

We are creating this feedback issue in preparation of the deprecation and subsequent removal, in case any issues arise between the 17.3 to the 18.0 release in relation to compliance pipelines.

Timeline / Important Dates

Together with our communication plan for this deprecation and migration, we aim to be fully transparent with the stages of work so that customers are well aware, ahead of time, what stage of the plan we are in and when they can expect the deprecation and migration to be fully complete:

Related Issues/MRs/Epics

What impact will this have on users?

Between 17.3 and 18.0, users can still create compliance pipelines but they will be progressively warned that it will be deprecated and guided to using pipeline execution policy instead. From the 18.0 release, users will not be able to create compliance pipelines any longer.

We will be implementing a reverse feature flag for any customer that did not have sufficient time to move their compliance pipelines to pipeline execution policy type by the 18.0 release. This reverse feature flag will be in place up till the 18.2 release, where we remain confident that all users at that point would've moved their compliance pipelines to pipeline execution policy.

DRIs/Contacts for questions

Edited by 🤖 GitLab Bot 🤖