From dbe452c4f186136fb14c4c31aa60f54be88a86bf Mon Sep 17 00:00:00 2001 From: Nathan Rosandich <nrosandich@gitlab.com> Date: Fri, 10 Mar 2023 06:37:53 +0000 Subject: [PATCH] Add compliance pipeline limitation --- doc/user/group/compliance_frameworks.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/doc/user/group/compliance_frameworks.md b/doc/user/group/compliance_frameworks.md index f5c0597adf5ac..9bde41171f908 100644 --- a/doc/user/group/compliance_frameworks.md +++ b/doc/user/group/compliance_frameworks.md @@ -223,6 +223,12 @@ include: # Execute individual project's configuration (if project contains .git The `rules` configuration in the `include` definition avoids circular inclusion in case the compliance pipeline must be able to run in the host project itself. You can leave it out if your compliance pipeline only ever runs in labeled projects. +#### Compliance pipelines and custom pipeline configurations + +Compliance pipelines don't run when an included project pipeline uses an external +[custom CI/CD configuration file](../../ci/pipelines/settings.md#specify-a-custom-cicd-configuration-file). For more information, see +[issue 393960](https://gitlab.com/gitlab-org/gitlab/-/issues/393960). + #### Compliance pipelines in merge requests originating in project forks When a merge request originates in a fork, the branch to be merged usually only exists in the fork. -- GitLab