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

Renaming maven installation breaks build jobs which use it

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • maven-plugin
    • None
    • Hudson ver. 1.371

      Steps to reproduce:
      1) Add maven 2 installation named e.g. "Maven 2.2.1"
      2) Create a maven 2 build job for a correct maven 2 project, and make use of maven 2 installed in step 1
      3) Run build from step 2, and it is successful
      4) Manage hudson, and rename maven 2 installation to e.g. "Apache Maven 2.2.1"
      5) Run the same build from step 2, and it fails with following error message:

      "ERROR: A Maven installation needs to be available for this project to be built.
      Either your server has no Maven installations defined, or the requested Maven version does not exist."

      It seems that some references do not get updated when maven installation is renamed.

      Workaround is to change job's maven to another installation, save the change, and then edit job again reverting the change and save it again - after this job runs same as before installation was renamed.

          [JENKINS-7205] Renaming maven installation breaks build jobs which use it

          kaosko added a comment -

          Since the bug is relatively old and I just run into it, confirming it's still an issue with Jenkins ver. 1.420. Annoying but the workaround is simple if you just know what to do.

          kaosko added a comment - Since the bug is relatively old and I just run into it, confirming it's still an issue with Jenkins ver. 1.420. Annoying but the workaround is simple if you just know what to do.

          Carlo de Wolf added a comment -

          Note that changing the "Maven Version" in the job configuration also works out. (Change it to for example to Maven 3 then back to Maven 2 or vica versa.)

          Carlo de Wolf added a comment - Note that changing the "Maven Version" in the job configuration also works out. (Change it to for example to Maven 3 then back to Maven 2 or vica versa.)

          Happens with Jenkins LTS 1.565.1. Even renaming it back to the original name does not fix the builds. You have to go into each job and select the proper Maven version again!

          Konrad Windszus added a comment - Happens with Jenkins LTS 1.565.1. Even renaming it back to the original name does not fix the builds. You have to go into each job and select the proper Maven version again!

            Unassigned Unassigned
            sslavic Stevo Slavić
            Votes:
            4 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: