[JIRA] (JENKINS-15293) Can't configure Maven Installations on Jenkins ver. 1.483 after upgrade from 1.470

Jeroen Ferdinandus created JENKINS-15293

Can't configure Maven Installations on Jenkins ver. 1.483 after upgrade from 1.470

Issue Type:	Bug
Assignee:	Unassigned
Attachments:	hudson.tasks.Maven.xml
Components:	maven
Created:	25/Sep/12 7:17 AM
Description:	After configuring Maven installations (with installer from apache) and clicking save, the Maven installations aren't saved. Logging on fine doesnt produce any reason about the problem. Manually copying an older hudson.tasks.Maven.xml does not seem to work either. Looking at recent bug fixes, I see that JENKINS-14510 got integrated in this build. I will try installing 1.482 and see if it resolves the problem.
Environment:	Jenkins 1.483, Ubuntu
Project:	Jenkins
Priority:	Critical
Reporter:	Jeroen Ferdinandus

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

Jeroen Ferdinandus updated JENKINS-15293

Can't configure Maven Installations on Jenkins ver. 1.483 after manual upgrade from 1.470

Change By:	Jeroen Ferdinandus (25/Sep/12 7:19 AM)
Summary:	Can't configure Maven Installations on Jenkins ver. 1.483 after  manual  upgrade from 1.470
Environment:	Jenkins 1.483, Ubuntu  12.04 LTS, running Jenkins standalone with Java.

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

Jeroen Ferdinandus updated JENKINS-15293

Can't configure Maven Installations on Jenkins ver. 1.483 after manual upgrade from 1.470

Change By:

Jeroen Ferdinandus (25/Sep/12 7:32 AM)

Description:

After configuring Maven installations (with installer from apache) and clicking save, the Maven installations aren't saved. Logging on fine doesnt produce any reason about the problem. Manually copying an older hudson.tasks.Maven.xml  does not seem to work either  works .    Looking at recent bug fixes, I see that JENKINS-14510 got integrated in this build. I will try installing 1.482 and see if it resolves the problem.

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

Jeroen Ferdinandus commented on JENKINS-15293

Can't configure Maven Installations on Jenkins ver. 1.483 after manual upgrade from 1.470

In 1.482 it is possible to add new Maven installations.

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

Jeroen Ferdinandus updated JENKINS-15293

Can't configure Maven Installations on Jenkins ver. 1.483 after manual upgrade from 1.470

Change By:	Jeroen Ferdinandus (25/Sep/12 8:01 AM)
Priority:	Critical Blocker

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

 

Jeroen Ferdinandus edited a comment on JENKINS-15293

Can't configure Maven Installations on Jenkins ver. 1.483 after manual upgrade from 1.470

In 1.482 it is possible to add new Maven installations. After I upgrade to 1.843 again and try adding a new Maven installation, all previously added Maven installations are removed.

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

John Harvey commented on JENKINS-15293

Can't configure Maven Installations on Jenkins ver. 1.483 after manual upgrade from 1.470

Same issue seen on Debian 6.0.5. Jenkins 1.483 has a bug that the config is unable to be saved, resulting in no jobs able to be run. Downgrading to 1.482 also fixed it.

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

Michael Fraefel commented on JENKINS-15293

Can't configure Maven Installations on Jenkins ver. 1.483 after manual upgrade from 1.470

The same on Windows 2003 Server.

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

Jeroen Ferdinandus updated JENKINS-15293

Can't configure Maven Installations on Jenkins ver. 1.483

Updated title to reflect the general problem with 1.483, since it seems it is not related to the upgrade from 1.470.
Change By:	Jeroen Ferdinandus (27/Sep/12 7:44 AM)
Summary:	Can't configure Maven Installations on Jenkins ver. 1.483  after manual upgrade from 1.470

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

Mirko Friedenhagen commented on JENKINS-15293

Can't configure Maven Installations on Jenkins ver. 1.483

Downgrading to 1.482 fixed this for me as well on Ubuntu 10.04 LTS.

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

Mirko Friedenhagen updated JENKINS-15293

Can't configure Maven Installations on Jenkins ver. 1.483, 1.484

Change By:	Mirko Friedenhagen (01/Oct/12 8:08 AM)
Summary:	Can't configure Maven Installations on Jenkins ver. 1.483 , 1.484
Environment:	Jenkins 1.483, Ubuntu 12.04 LTS, running Jenkins standalone with Java. Jenkins 1.484, Ubuntu 10.04 LTS, running Jenkins standalone with Java.

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

Mirko Friedenhagen commented on JENKINS-15293

Can't configure Maven Installations on Jenkins ver. 1.483

Still there in 1.484. That's really annoying.

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

Mirko Friedenhagen commented on JENKINS-15293

Can't configure Maven Installations on Jenkins ver. 1.483, 1.484

Hello, I inspected https://github.com/mpapo/jenkins/commit/01482bf3de81f539b7ae4746fd127ca75915a726 and found the problem: While all Maven installations have a name, those being resolved automatically (e.g. downloaded from Apache directly) do not have a home field set explicitly. So the for loop just removes these from tmpList and the list is empty in the end. Maven installations given manually, e.g. you provide a path will stay. Regards Mirko

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

Pailloncy Michaël assigned JENKINS-15293 to Pailloncy Michaël

Can't configure Maven Installations on Jenkins ver. 1.483, 1.484

Change By:	Pailloncy Michaël (01/Oct/12 10:35 AM)
Assignee:	Pailloncy Michaël

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

SCM/JIRA link daemon commented on JENKINS-15293

Can't configure Maven Installations on Jenkins ver. 1.483, 1.484

Code changed in jenkins User: Olivier Lamy Path: core/src/main/java/hudson/tasks/Maven.java http://jenkins-ci.org/commit/jenkins/7daa5ef1b245fd7a8887bbc6274be080a52a4d23 Log: Merge pull request #581 from mpapo/JENKINS-15293 Fixed JENKINS-15293 Thanks Compare: https://github.com/jenkinsci/jenkins/compare/14098be5db0e...7daa5ef1b245

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

SCM/JIRA link daemon commented on JENKINS-15293

Can't configure Maven Installations on Jenkins ver. 1.483, 1.484

Code changed in jenkins User: Olivier Lamy Path: changelog.html http://jenkins-ci.org/commit/jenkins/c0df15ab38c2fef8592d38451cef0ba68ebc64d0 Log: changelog entry for JENKINS-15293

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

cowwoc commented on JENKINS-15293

Can't configure Maven Installations on Jenkins ver. 1.483, 1.484

Olivier, Maybe I misunderstood, but shouldn't the OR in the condition be an AND? That is, we only want to remove installations if they have an empty name and an empty home directory. Right?

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

Pailloncy Michaël commented on JENKINS-15293

Can't configure Maven Installations on Jenkins ver. 1.483, 1.484

The bug https://issues.jenkins-ci.org/browse/JENKINS-14510 is related to a NPE on Maven installation name. So, I think just a check on the maven installation name will be sufficient.

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

Deepak Mahale commented on JENKINS-15293

Can't configure Maven Installations on Jenkins ver. 1.483, 1.484

Hi, I had a similar problem with ANT, JDK, MSBuild installation configs (all of which were already installed and i had added the proper paths to each) when i upgraded Jenkins. I was also experimenting with the files so even the uninstall and install had stopped working and the Jenkins service stopped altogether. I followed the the steps mentioned below and it resolved the problem for me: 1. Uninstall Jenkins 2. Restart system 3. Delete the Jenkins Installation directory 4. Manually remove the registry keys using 'regedit' 5. Restart system 6. Install Jenkins From then on i haven't had problems with updates and configs. I've never used Maven and do not know if this is a separate issue. Regards

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

Mirko Friedenhagen commented on JENKINS-15293

Can't configure Maven Installations on Jenkins ver. 1.483, 1.484

Deepak Mahale: I would not know that Jenkins saves it's information about helper programs in the Windows registry. I think you would be better off opening another issue as the Maven bug is clearly gone. You might link to this item (see "More Actions"). And it would be helpful if you stated which registry keys you did delete.

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