failed Pipeline #3083 triggered by
Samten Gyeltshen
@Samten_Govtech

add files

11 jobs for master in 0 seconds (queued for 100 minutes and 11 seconds)
Status Name Job ID Coverage
  Build
failed build #16852

 
  Test
skipped bandit-sast #16855
allowed to fail
skipped brakeman-sast #16856
allowed to fail
failed code_quality #16854
allowed to fail

skipped eslint-sast #16857
allowed to fail
skipped flawfinder-sast #16858
allowed to fail
skipped secret_detection #16862
allowed to fail
skipped security-code-scan-sast #16859
allowed to fail
skipped semgrep-sast #16860
allowed to fail
skipped spotbugs-sast #16861
allowed to fail
failed test #16853

 
Name Stage Failure
failed
code_quality Test There has been a timeout failure or the job got stuck. Check your timeout limits or try again
No job log
failed
test Test There has been a timeout failure or the job got stuck. Check your timeout limits or try again
No job log
failed
build Build There has been a timeout failure or the job got stuck. Check your timeout limits or try again
No job log

Speed up your pipelines with Needs relationships

Using the needs keyword makes jobs run before their stage is reached. Jobs run as soon as their needs relationships are met, which speeds up your pipelines.

If you add needs to jobs in your pipeline you'll be able to view the needs relationships between jobs in this tab as a Directed Acyclic Graph (DAG).

There are no test reports for this pipeline

You can configure your job to use unit test reports, and GitLab displays a report here and in the related merge request.