Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-15293

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

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Blocker Blocker
    • maven-plugin
    • None
    • Jenkins 1.483, Ubuntu 12.04 LTS, running Jenkins standalone with Java.
      Jenkins 1.484, Ubuntu 10.04 LTS, running Jenkins standalone with Java.

      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 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.

          [JENKINS-15293] Can't configure Maven Installations on Jenkins ver. 1.483, 1.484

          Still there in 1.484. That's really annoying.

          Mirko Friedenhagen added a comment - Still there in 1.484. That's really annoying.

          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

          Mirko Friedenhagen added a comment - 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

          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

          SCM/JIRA link daemon added a comment - 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

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

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Olivier Lamy Path: changelog.html http://jenkins-ci.org/commit/jenkins/c0df15ab38c2fef8592d38451cef0ba68ebc64d0 Log: changelog entry for JENKINS-15293

          cowwoc added a comment -

          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?

          cowwoc added a comment - 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?

          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.

          Michael Pailloncy added a comment - 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.

          Deepak Mahale added a comment -

          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

          Deepak Mahale added a comment - 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

          deepak: 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.

          Mirko Friedenhagen added a comment - deepak : 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.

          Jeroen Ferdinandus added a comment - - edited

          The update to Jenkins 1.485 has resolved this issue.

          Jeroen Ferdinandus added a comment - - edited The update to Jenkins 1.485 has resolved this issue.

          Bug due to a correction made for https://issues.jenkins-ci.org/browse/JENKINS-14510 -> resolved since 1.485

          Michael Pailloncy added a comment - Bug due to a correction made for https://issues.jenkins-ci.org/browse/JENKINS-14510 -> resolved since 1.485

            mpapo Michael Pailloncy
            jeroenferdinandus Jeroen Ferdinandus
            Votes:
            9 Vote for this issue
            Watchers:
            16 Start watching this issue

              Created:
              Updated:
              Resolved: