![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Affects Versions:
|
current |
|
Assignee:
|
Unassigned |
|
Components:
|
jobgenerator |
|
Created:
|
10/Jun/14 3:23 PM
|
|
Description:
|
I have around a dozen job generator jobs started by a starter job. All of these job generator jobs have the custom workspace directory set with multiple variables inside (taken from the starter job), and these get expanded well in the generated jobs.
Something happens after a few invocations, and the generated jobs don't get the custom workspace setting. This causes build FAILURE, and when I check the reason, I usually find that the custom workspace setting has disappeared from the generator jobs. Sometimes reloading the configuration from disk works, but sometimes the setting disappears first from the config.xml files while still showing up in the job generator configuration page. The change occurs in every generator job started by the starter job.
Other configuration options seem unaffected.
Version: 1.22 (had the same issue with 1.20)
|
|
Environment:
|
Jenkins 1.549 on Ubuntu Precise
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Dezso Moldvai
|
|
|
|
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.
