[INTPAK-92] Trigger test-rpm to run on result of build-rpm-* jobs Created: 21/Nov/17 Updated: 15/Jan/18 Resolved: 15/Jan/18 |
|
| Status: | Closed |
| Project: | integration-packaging |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Medium |
| Reporter: | Daniel Farrell | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Epic Link: | Complete CD pipelines | ||||||||||||||||
| Description |
|
Every time the packaging-build-rpm or packaging-build-rpm-snap jobs produce an RPM, test it with the packaging-test-rpm job. |
| Comments |
| Comment by Daniel Farrell [ 15/Jan/18 ] |
|
Turned out it was a better idea to do the tests in the build job itself so we can avoid pushing RPMs to Nexus if they have problems. This was done in |