[INTPAK-151] Support custom RPM builds by unprivileged users Created: 19/Mar/18 Updated: 29/Jun/18 Resolved: 29/Jun/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: | Daniel Farrell |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Description |
|
As it stands, users who want to use the automated jobs to build custom RPMs need to have permission to build on RelEng Jenkins, which is highly restricted. There isn't a way to get the RPMs build in sandbox runs, they are discarded. We need a way for someone without RelEng Jenkins permissions to get the custom RPMs they build. Could do this by pushing sandbox RPMs to a "scratch" silo on Nexus. Or maybe hosting them with the other log artifacts. |
| Comments |
| Comment by Daniel Farrell [ 27/Jun/18 ] |
|
It's now possible to push to scratch repos like https://nexus.opendaylight.org/content/repositories/opendaylight-epel-7-x86_64-devel/org/opendaylight/integration-packaging/opendaylight/ from the sandbox. Need to document, then this is done. |