| Status | Job ID | Name | Coverage | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Static Analysis | |||||||||
| passed |
#17992
cross
|
gitattributes |
00:00:01
|
|
|||||
| passed |
#17993
cross
|
gitignore |
00:00:00
|
|
|||||
| passed |
#17996
cross
|
head_log |
00:00:00
|
|
|||||
| passed |
#17998
cross
|
head_whitesp |
00:00:00
|
|
|||||
| passed |
#17994
cross
|
license |
00:00:00
|
|
|||||
| passed |
#17997
cross
|
makefile |
00:00:00
|
|
|||||
| passed |
#17995
cross
|
versionnum |
00:00:01
|
|
|||||
| Softload | |||||||||
| passed |
#17999
cross
|
softload |
00:00:05
|
|
|||||
| passed |
#18000
cross
|
softload_gnu |
00:00:05
|
|
|||||
| Disc | |||||||||
| failed |
#18001
cross
allowed to fail
|
disc_BuildHost |
00:00:14
|
|
|||||
| Cleanup | |||||||||
| passed |
#18002
cross
|
cleanup |
00:00:01
|
|
|||||
| Name | Stage | Failure | ||
|---|---|---|---|---|
|
failed
|
disc_BuildHost | Disc | ||
|
||||
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).