Skip to content

Fix and improve compliance pipeline example

Greg Myers requested to merge docs-compliance-framework-pipeline-example into master

What does this MR do?

Improves the compliance framework .gitlab-ci.yml example by:

  • ensuring consistent spacing
  • dropping unessecary/redundant config (when: always & allow_failure: false are default)
  • change sast job name to prevent customers from directly overriding and adding scripts to the config-only default sast job
  • note that including an individual projects' config as part of compliance pipeline will only work if the project has it's own .gitlab-ci.yml file.

As a bonus, I fixed up the markdown table formatting on this page.

This MR was created to address customer problems/misunderstandings w/r/t the example in our docs. Specifically this Support ticket and a Federal Support Ticket

Screenshots (strongly suggested)

Does this MR meet the acceptance criteria?

Conformity

Availability and Testing

Security

Does this MR contain changes to processing or storing of credentials or tokens, authorization and authentication methods or other items described in the security review guidelines? If not, then delete this Security section.

  • Label as security and @ mention @gitlab-com/gl-security/appsec
  • The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
  • Security reports checked/validated by a reviewer from the AppSec team

Merge request reports