Bug 1719477
| Summary: | clean up protocol specified in pom.xml for various jenkins plugin builds | |||
|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Gabe Montero <gmontero> | |
| Component: | ImageStreams | Assignee: | Gabe Montero <gmontero> | |
| Status: | CLOSED ERRATA | QA Contact: | XiuJuan Wang <xiuwang> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | 3.11.0 | CC: | aos-bugs, jokerman, mmccomas, wzheng | |
| Target Milestone: | --- | |||
| Target Release: | 3.11.z | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Bug Fix | ||
| Doc Text: |
Cause: the pom.xml of some of the openshift jenkins plugins had http:// references instead of https:// references for some of its build time dependencies
Consequence: when building the plugins, dependency downloads would occur over http instead of https
Fix: the pom.xml references were corrected
Result: any dependency downloads during building of the plugins now always occur over https
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1719795 1723535 (view as bug list) | Environment: | ||
| Last Closed: | 2019-07-23 19:56:23 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1719795, 1723535 | |||
|
Description
Gabe Montero
2019-06-11 22:29:52 UTC
PR https://github.com/openshift/jenkins/pull/868 is up Once that merges, I'll post the ART request link for updating the plugin RPM PR has merged .... ART req for RPM update https://jira.coreos.com/browse/ART-671 Do regression with pipeline build, login with openshift oauth, sync builds between openshift， no issue found. Test with openshift3/jenkins-2-rhel7:v3.11(v3.11.128-2) Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:1753 |