![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
Unassigned |
|
Components:
|
subversion-plugin |
|
Created:
|
12/Feb/15 8:58 PM
|
|
Description:
|
The subversion plug-in of course resolves environment variables for updating the working copy. However, when using SCM polling env vars are not resolved.
I have found the following comment in Jenkins-13075:
Michael Clarke added a comment - 18/Nov/12 9:37 AM
During polling the plugin isn't provided the environmental variables so wouldn't be able to do an expansion for you. This is partly because polling is supposed to be a task that doesn't require user input so there would be no way of handling user defined parameters.
I don't understand the problem with SCM polling allowing a dependency on environment variables. This is not dynamic user input, but a static environment variable in Jenkins. Polling and the environment variable both reside in Jenkins. Why can polling then not be coded to access an environment variable? Perhaps the other "partly" of the explanation would make more sense.
So this may end up being resolved through explanation, but for now I'm creating it as a bug. The logic behind the omission escapes me so my perspective at the moment is defect.
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Minor]() Minor
|
|
Reporter:
|
Tim Bradt
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[email protected].
For more options, visit
https://groups.google.com/d/optout.
