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

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

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Blocker
    • Resolution: Fixed
    • 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.

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

      Attachments

        Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-15312 maven installation settings get lost

          • Critical - Crashes, loss of data, severe memory leak.
          • Resolved
          is related to

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-14510 NPE at hudson.maven.MavenModuleSet.getMaven(MavenModuleSet.java:982)

          • Trivial - Cosmetic problem like misspelt words or misaligned text.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            View 10 older comments
            mpapo 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.

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

            mfriedenhagen 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.
            jeroenferdinandus Jeroen Ferdinandus added a comment - - edited

            The update to Jenkins 1.485 has resolved this issue.

            jeroenferdinandus Jeroen Ferdinandus added a comment - - edited The update to Jenkins 1.485 has resolved this issue.
            mpapo 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 added a comment - Bug due to a correction made for https://issues.jenkins-ci.org/browse/JENKINS-14510 -> resolved since 1.485

            People

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

              Dates

                Created:
                Updated:
                Resolved: