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

The "Root POM" field value in the Build section of a Maven job configuration is not being read in.

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • maven-plugin

      I'm currently using version 1.467. The value in the "Root POM" field in the "Build" section of a Maven job configuration is not being read in when the configuration is loaded. If you modify the job configuration, the "Root POM" field is blank. If you fill in the "Root POM" field and save, the job will work correctly, but if you neglect to fill it in, even if you modify something else within the job, it will break the build. This is causing some of our jobs to fail b/c the pom.xml file that needs to be executed is not in the root folder of the Workspace. I believe this was introduced in version 1.466 with the following snippet from the release notes "Maven plugin: expand variables in "Room POM" field (issue 13822)".

          [JENKINS-14054] The "Root POM" field value in the Build section of a Maven job configuration is not being read in.

          Pete Hammond added a comment -

          I upgraded to 1.467 from 1.465 yesterday (06-06-2012) and the same thing is happening on all of my jobs.

          The root pom field is not being retained, I fill it in run a build, it works. the next time a developer checks in the job runs and fails with pom not found.

          Pete Hammond added a comment - I upgraded to 1.467 from 1.465 yesterday (06-06-2012) and the same thing is happening on all of my jobs. The root pom field is not being retained, I fill it in run a build, it works. the next time a developer checks in the job runs and fails with pom not found.

          Harry Braun added a comment -

          We can't use the sonar-plugin and everytime we open the configuration the root pom is empty. So we think about going back to 1.465..

          Harry Braun added a comment - We can't use the sonar-plugin and everytime we open the configuration the root pom is empty. So we think about going back to 1.465..

          edbras added a comment -

          Same experience here...
          Simple open the project, fill the root pom field, press save and open the config page again -> root pom field empty. However it's used, so it's only a display issue I quess, and it uses the empty value when pressing the save button again.
          So you must always fill it in as a workaround if you want to presse the save/appy button.

          edbras added a comment - Same experience here... Simple open the project, fill the root pom field, press save and open the config page again -> root pom field empty. However it's used, so it's only a display issue I quess, and it uses the empty value when pressing the save button again. So you must always fill it in as a workaround if you want to presse the save/appy button.

          Same here - a rather painful regression.

          Michael Paesold added a comment - Same here - a rather painful regression.

          evernat added a comment -

          I do not reproduce the issue with a recent Jenkins version.
          Do you reproduce it?

          evernat added a comment - I do not reproduce the issue with a recent Jenkins version. Do you reproduce it?

          No, I can't reproduce either. Earliest tested version is LTS 1.609.3. That and all later versions are good.

          I propose to resolve this issue. Any objections?

          Michael Paesold added a comment - No, I can't reproduce either. Earliest tested version is LTS 1.609.3. That and all later versions are good. I propose to resolve this issue. Any objections?

            Unassigned Unassigned
            bpmericle Brian Mericle
            Votes:
            5 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: