[INTPAK-115] Add RPM tests to RPM build job, not just standalone job Created: 11/Dec/17 Updated: 15/Jan/18 Resolved: 13/Dec/17 |
|
| Status: | Closed |
| Project: | integration-packaging |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Medium |
| Reporter: | Daniel Farrell | Assignee: | Daniel Farrell |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
We shouldn't publish RPMs that don't pass our tests. The only way I can think of to do that is by gating publishing to Nexus during the actual job that publishes. If we check in a second job after already pushing (as we currently do) it'll already be too late, the RPM is being consumed. |
| Comments |
| Comment by Daniel Farrell [ 12/Dec/17 ] |