[IEC-29] [CI] Stop running subsequent jobs if deployment failed Created: 29/Jan/20 Updated: 29/Jan/20 |
|
| Status: | To Do |
| Project: | Integrated Edge Cloud |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Medium |
| Reporter: | Cristina Pauna | Assignee: | Cristina Pauna |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
Currently we have several jobs running in CI subsequently (e.g. [1]). The first job is the deploy, and the rest are assuming that the deploy has been successful. That is not always the case, so we should make sure that the subsequent jobs are not running, wasting CI cycles.
[1] https://jenkins.akraino.org/view/iec/job/iec-type2-fuel-virtual-ubuntu1604-daily-master/ |