Expand environment variables in repository URL.#38
Conversation
…ring validation check, affecting also entering of credentials. This should allow you to use the same $JENKINS_HOME contents while switching the physical location of your Subversion server using a startup environment. (Has no effect when "Validate repository URLs up to the first variable name" is checked.)
|
Jenkins » subversion-plugin #116 SUCCESS |
|
Jenkins » subversion-plugin #117 UNSTABLE |
|
Jenkins » subversion-plugin #118 UNSTABLE |
|
Jenkins » subversion-plugin #131 UNSTABLE |
|
I am not sure what the |
There was a problem hiding this comment.
Actually this is wrong, because getLocations ignores build when env is set. Need to consider both combined.
|
Jenkins » subversion-plugin #138 UNSTABLE |
…ild). A user reported that $SVN_REVISION_1 etc. were not getting set otherwise.
|
Jenkins » subversion-plugin #139 SUCCESS |
|
Sometimes I review PRs here, but there are several areas which I'm not familiar with, either, and variable expansion is definitely one of them. |
|
Jenkins » subversion-plugin #143 SUCCESS |
…g locations for SVN_* variables.
|
Jenkins » subversion-plugin #144 FAILURE |
|
Thank you for a pull request! Please check this document for how the Jenkins project handles pull requests |
|
Jenkins » subversion-plugin #155 UNSTABLE |
|
Reporter of original issue seems satisfied with the current state of this branch. |
There was a problem hiding this comment.
Better to put the recursive into ModuleLocation#getExpandedLocation(EnvVars)?
There was a problem hiding this comment.
Would be possible. On the other hand, this would be less efficient—would need to make a defensive copy of the env argument, and the logic would be needlessly repeated for each location. Also this would make a behavioral change to a lower-level method which is only apparently called from here. So unless there is a particular use case that requires the call to resolve to be pushed down, I think it makes more sense here.
|
As far as I'm able to understand this, looks fine. |
Expand environment variables in repository URL.
|
BTW any plans for a trunk release? (I know the |
|
Done. After I had to skip a version number and lost another hour of my life because of http://jira.codehaus.org/browse/MRELEASE-812 :( |
|
Just be thankful your |
Expand environment variables in repository URL in job confguration during validation check, affecting also entering of credentials.
This should allow you to use the same
$JENKINS_HOMEcontents while switching the physical location of your Subversion server using a startup environment.(Has no effect when Validate repository URLs up to the first variable name is checked.)
Also expands build variables (e.g. those defined in a containing folder property) when defining
SVN_*variables, which would otherwise go unset.Might solve JENKINS-11667.