last commit
| Status | Name | Job ID | Coverage | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Build | |||||||||
| failed | build |
#8080
|
00:00:17
|
|
|||||
| Test | |||||||||
| failed | code_quality |
#8082
allowed to fail
|
00:00:20
|
|
|||||
| skipped | eslint-sast |
#8083
allowed to fail
|
|
||||||
| skipped | nodejs-scan-sast |
#8084
allowed to fail
|
|
||||||
| skipped | secret_detection |
#8086
allowed to fail
|
|
||||||
| skipped | semgrep-sast |
#8085
allowed to fail
|
|
||||||
| failed | test |
#8081
|
00:01:11
|
|
|||||
| Name | Stage | Failure | ||
|---|---|---|---|---|
|
failed
|
code_quality | Test | ||
|
||||
|
failed
|
build | Build | ||
|
||||
|
failed
|
test | Test | ||
|
||||
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).
You can configure your job to use unit test reports, and GitLab displays a report here and in the related merge request.