Bug 1510908
Summary: | jenkinsURL not available upon deployment | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Ruben Romero Montes <rromerom> |
Component: | Build | Assignee: | Gabe Montero <gmontero> |
Status: | CLOSED NOTABUG | QA Contact: | Wenjing Zheng <wzheng> |
Severity: | low | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.6.0 | CC: | aos-bugs, bparees, gmontero, rromerom |
Target Milestone: | --- | ||
Target Release: | 3.8.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-12-15 10:53:09 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: |
Description
Ruben Romero Montes
2017-11-08 12:35:33 UTC
The only way I see this happening is a hack where one of our plugins (the login plugin would probably be the best choice) calls Jenkins.getInstance().getRootUrl() for the value and then populates this file. I'm curious how/if this works in a typical jenkins deployment. What creates the file and when? If this is jenkins behavior (that the file is not created until a job is manually created) then i don't see why we would be responsible for doing anything differently. From what i can tell from a little experimenting, this is totally driven by jenkins behavior and you'd have to open an issue w/ upstream jenkins to get them to change how/when that file is created. I ran a simple non-scientific test by running the jenkins.war by itself. The jenkins.model.JenkinsLocationConfiguration.xml file is not created until I make a change to the config and save it. Issue filed on Jenkins project: https://issues.jenkins-ci.org/browse/JENKINS-48079 Thanks for the effort |