![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
Gregory Boissinot
|
|
Components:
|
envinject |
|
Created:
|
09/May/13 4:02 PM
|
|
Description:
|
Upgraded from EnvInject 1.0 to 1.85 and builds stopped working correctly.
Each build was using the wrong workspace, and all builds were trying to use this same incorrect workspace. The workspace was a valid workspace for a different job, but not the job that I was running. Each time I reloaded jenkins, the workspace changed but all builds still tried to use that same incorrect workspace.
I had the following in my ant script:
<property environment="env"/>
<property name="job.wspath" value="${env.WORKSPACE}"/>
job.wspath was being set to the workspace of the wrong job, because the WORKSPACE env variable was getting hosed by the new EnvInject.
I downgraded EnvInject from 1.85 to 1.0 and the problem was resolved.
|
|
Environment:
|
Linux RedHat 5. Jenkins 1.510. EnvInject 1.85
|
|
Project:
|
Jenkins
|
|
Labels:
|
plugin
envinject
workspace
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Joel Wheeler
|
|
|
|
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/groups/opt_out.
