-
Bug
-
Resolution: Fixed
-
Minor
-
None
-
-
display-url-api 2.3.4
As a user, I want to override URLs injected by the plugin into environment variables
There is a DisplayURLProvider#getDefault() API which can be used to retrieve the provider extension defined by the user. There is also a DisplayURLProvider#get() which always returns the default provider instance.
The second method is used in https://github.com/jenkinsci/display-url-api-plugin/blob/master/src/main/java/org/jenkinsci/plugins/displayurlapi/EnvironmentContributorImpl.java which contributes environment variables. It means that the provider implementations won't be taken into account.
This is somewaht related to JENKINS-41919, but it is not reported as defect
- causes
-
JENKINS-69006 Impossible to configure default display URL provider but keep redirection (regression in 2.3.4)
-
- Closed
-
- is duplicated by
-
JENKINS-41919 System env/property for default implementation not usefull
-
- Closed
-
- relates to
-
JENKINS-56406 Expose artifacts and test display URLs in environment variables
-
- Resolved
-
[JENKINS-64119] Display URL Plugin does not consult with DisplayURLProvider implementations when injecting environment variables
Link |
New:
This issue relates to |
Link |
New:
This issue relates to |
Assignee | Original: James Dumay [ jamesdumay ] | New: Olivier Lamy [ olamy ] |
Comment |
[ {{[~oleg_nenashev] user defined means class implementation defined via sysproperty `jenkins.displayurl.provider` or }}PreferredProviderUserProperty#getConfiguredProvider {{?}}
or both? :) ] |
Link |
New:
This issue causes |
Released As | New: display-url-api 2.3.4 | |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Link |
New:
This issue is duplicated by |
Link |
Original:
This issue relates to |