| Status | Job ID | Name | Coverage | ||||||
|---|---|---|---|---|---|---|---|---|---|
| External | |||||||||
| failed |
#114697
external
|
ERP5.UnitTest-Master |
|
||||||
| passed |
#114684
external
|
SlapOS.Eggs.UnitTest-Master.Python2 |
01:26:28
|
||||||
| passed |
#114727
external
|
SlapOS.Eggs.UnitTest-Master.Python3 |
00:13:10
|
||||||
| passed |
#114679
external
retried
|
SlapOS.Eggs.UnitTest-Master.Python2 |
|
||||||
| passed |
#114667
external
retried
|
SlapOS.Eggs.UnitTest-Master.Python3 |
|
||||||
| passed |
#114672
external
retried
|
SlapOS.Eggs.UnitTest-Master.Python3 |
01:58:54
|
||||||
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).