Loading
Enable cancel_pipelines_when_policy_disabled by default
What does this MR do and why?
Enables the cancel_pipelines_when_policy_disabled feature flag by default. The flag type changes from gitlab_com_derisk to beta because gitlab_com_derisk flags cannot be default-enabled (lib/feature/definition.rb raises for types with can_be_default_enabled: false).
With this change, running policy schedule pipelines are automatically cancelled when a pipeline execution schedule policy is disabled or unlinked from a project, without requiring manual flag activation.
A follow-up MR (!244639 (merged)) removes the flag entirely once this has been verified.
References
- Feature issue: #560629 (closed)
- Flag introduced by: !236748 (merged)
- Flag removal MR: !244639 (merged)
Screenshots or screen recordings
| Before | After |
|---|---|
| N/A | N/A |
How to set up and validate locally
- Create a group with a security policy project and a pipeline execution schedule policy linked to a project.
- Wait for a scheduled policy pipeline to start running in the project.
- Disable the policy (or unlink the project from the policy scope).
- Verify the running policy schedule pipeline is cancelled, without any feature flag setup.
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist.