failed Pipeline #79023 triggered by
Lê Tuấn Anh
@rta_tuananh :speaker:

Init project

7 jobs for main in 0 seconds (queued for 75 minutes and 3 seconds)
latest Auto DevOps
Status
Job
Stage
Name
Duration
Coverage
allowed to fail
test
secret_detection
allowed to fail
test
spotbugs-sast
allowed to fail
test
semgrep-sast
allowed to fail
test
container_scanning
allowed to fail
test
code_quality
test
test
build
build
Name
Stage
Failure
test
There has been a timeout failure or the job got stuck. Check your timeout limits or try again
      No job log
    
test
There has been a timeout failure or the job got stuck. Check your timeout limits or try again
      No job log
    
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.