Pipeline Failure After Group Transfer with Compliance Framework
Summary
When transferring a project with compliance framework enabled from one top-level group to another, pipelines fail to start due to hardcoded project paths in the compliance framework configuration. Removing the compliance framework resolves the issue, suggesting the paths are hardcoded within the framework itself.
Steps to reproduce
- Have a top-level group with compliance framework
- Have a project inside a subgroup under this group with compliance framework applied
- Transfer the subgroup (and its project) to a different top-level group that doesn't have the compliance framework configured
- The compliance framework is still attached to the project from the previous top-level group
Example Project
What is the current bug behavior?
After transferring a subgroup (and its project with compliance framework enabled) to a new top-level group it still has the compliance framework applied from the previous top-level group
There is no way to edit the compliance framework configuration on the new top-level group because the compliance framework doesn't exist there. The only solution is to completely remove the compliance framework from the project.
What is the expected correct behavior?
When a project with compliance framework is transferred to a new group the compliance framework should be removed from the project.
Relevant logs and/or screenshots
Pipeline cannot be run. Project path/to/project not found or access denied! Make sure any includes in the pipeline configuration are correctly defined.Output of checks
This bug happens on GitLab.com
Results of GitLab environment info
Expand for output related to GitLab environment info
Results of GitLab application Check
Expand for output related to the GitLab application check
CC @bcarranza