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

          Jeroen Ferdinandus created issue -
          Jeroen Ferdinandus made changes -
          Environment Original: Jenkins 1.483, Ubuntu New: Jenkins 1.483, Ubuntu 12.04 LTS, running Jenkins standalone with Java.
          Summary Original: Can't configure Maven Installations on Jenkins ver. 1.483 after upgrade from 1.470 New: Can't configure Maven Installations on Jenkins ver. 1.483 after manual upgrade from 1.470
          Jeroen Ferdinandus made changes -
          Description Original: 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.
          New: 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.

          Jeroen Ferdinandus added a comment - - edited

          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.

          Jeroen Ferdinandus added a comment - - edited 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.
          Jeroen Ferdinandus made changes -
          Priority Original: Critical [ 2 ] New: Blocker [ 1 ]

          John Harvey added a comment -

          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.

          John Harvey added a comment - 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.

          The same on Windows 2003 Server.

          Michael Fraefel added a comment - The same on Windows 2003 Server.

          Updated title to reflect the general problem with 1.483, since it seems it is not related to the upgrade from 1.470.

          Jeroen Ferdinandus added a comment - Updated title to reflect the general problem with 1.483, since it seems it is not related to the upgrade from 1.470.
          Jeroen Ferdinandus made changes -
          Summary Original: Can't configure Maven Installations on Jenkins ver. 1.483 after manual upgrade from 1.470 New: 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.

          Mirko Friedenhagen added a comment - Downgrading to 1.482 fixed this for me as well on Ubuntu 10.04 LTS.

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

              Created:
              Updated:
              Resolved: