Skip to content

Document allow_failure for Container Scanning

Adam Cohen requested to merge document-allow-failure-for-cs into master

What does this MR do?

This MR provides detailed information about using the allow_failure configuration option within the context of a Container Scanning job. The reason for this documentation change is to make the default behaviour of allow_failure more clear, and explain how to override it in the event that a user wants the pipeline to fail if vulnerabilities are found.

Related issues

#211925 (closed)

Author's checklist

Review checklist

All reviewers can help ensure accuracy, clarity, completeness, and adherence to the Documentation Guidelines and Style Guide.

1. Primary Reviewer

  • Review by a code reviewer or other selected colleague to confirm accuracy, clarity, and completeness. This can be skipped for minor fixes without substantive content changes.

2. Technical Writer

  • Optional: Technical writer review. If not requested for this MR, must be scheduled post-merge. To request for this MR, assign the writer listed for the applicable DevOps stage.

3. Maintainer

  1. Review by assigned maintainer, who can always request/require the above reviews. Maintainer's review can occur before or after a technical writer review.
  2. Ensure a release milestone is set.
  3. If there has not been a technical writer review, create an issue for one using the Doc Review template.

Merge request reports

Loading