|
|
 |
|
|
|
|
Issue Type:
|
 Bug
|
|
Affects Versions:
|
current |
|
Assignee:
|
Unassigned |
|
Components:
|
maven |
|
Created:
|
26/Sep/12 7:25 AM
|
|
Description:
|
After upgrading Jenkins to version 1.483, I see this behaviour:
Changing some (other) values on the Jenkins settings page, the Maven installation entries get lost after the save.
This results in broken maven build jobs, because they are missing their configured Maven installation.
Trying to reconfigure a Maven installation on the Jenkins settings page has no effect. After calling "save", the Maven entries disappear.
I have no log to present, because I had to downgrade Jenkins to version 1.481 to get my builds working.
|
|
Environment:
|
Linux, Java 1.6
|
|
Project:
|
Jenkins
|
|
Priority:
|
 Critical
|
|
Reporter:
|
lfischer
|
|
|
|
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
|
|
Locked
I worked around this by overriding jenkins/tools-folder and jenkins/hudson.tasks.Maven.xml from another setup and then restarting Jenkins.
If you save Jenkins config even without doing any changes, the file hudson.tasks.Maven.xml gets reset, and maven is not found by builds anymore.