Skip to content

Improve error message for Security Features with alias usage in ci file

Jannik Lehmann requested to merge jnnkl-ci-alias-error-handling into master

What does this MR do and why?

This MR solves: #379206 (closed)

It introduces an enhancement to the error message that is thrown in situations where Security Features are enabled, and a ci file is utilizing aliases. The update aims to make the error message more user-friendly by utilizing the user-facing error message utility.

Screenshots or screen recordings

before after
2023-03-23_12-29-52 2023-03-23_12-30-38

How to set up and validate locally

  • create a project which uses aliases in the ci-file 
 job1:
   cache: &any_name
     paths: [.]
   script: [pwd && date]  # or whatever

 job2:
   cache:
     <<: *any_name
   script: [pwd && date]  # or whatever
  • run a pipeline
  • go to Security & Compliance click on enable SAST or enable Secret Detection
  • see Error Message in Action

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Merge request reports