| Status | Job ID | Name | Coverage | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Static Analysis | |||||||||
| passed |
#90547
cross
|
copyright |
00:00:00
|
|
|||||
| passed |
#90540
cross
|
gitattributes |
00:00:00
|
|
|||||
| passed |
#90541
cross
|
gitignore |
00:00:00
|
|
|||||
| passed |
#90544
cross
|
head_log |
00:00:01
|
|
|||||
| passed |
#90542
cross
|
license |
00:00:00
|
|
|||||
| passed |
#90545
cross
|
makefile |
00:00:00
|
|
|||||
| passed |
#90543
cross
|
versionnum |
00:00:00
|
|
|||||
| passed |
#90546
cross
|
whitespace |
00:00:01
|
|
|||||
| Softload | |||||||||
| passed |
#90548
cross
|
softload |
00:00:05
|
|
|||||
| Cleanup | |||||||||
| passed |
#90549
cross
|
cleanup |
00:00:01
|
|
|||||
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).