init

13 jobs for master in 0 seconds (queued for 105 minutes and 49 seconds)

View job dependencies in the pipeline graph!

You can now group jobs in the pipeline graph based on which jobs are configured to run first, if you use the needs: keyword to establish job dependencies in your CI/CD pipelines. Learn how to speed up your pipeline with needs.

Provide feedback
Status Job ID Name Coverage
  Build
failed #3515
build

 
  Test
skipped #3518
allowed to fail
bandit-sast
skipped #3519
allowed to fail
brakeman-sast
failed #3517
allowed to fail
code_quality

skipped #3520
allowed to fail
eslint-sast
skipped #3521
allowed to fail
flawfinder-sast
skipped #3522
allowed to fail
nodejs-scan-sast
skipped #3523
allowed to fail
phpcs-security-audit-sast
skipped #3527
allowed to fail
secret_detection_default_branch
skipped #3524
allowed to fail
security-code-scan-sast
skipped #3525
allowed to fail
semgrep-sast
skipped #3526
allowed to fail
spotbugs-sast
failed #3516
test

 
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).