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

"Goals and Options" and "Root POM" not written to config.xml

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Blocker Blocker
    • maven-plugin
    • OS: Ubuntu 14.04
      Jenkins: 2.27 (installed & updated from official APT repo)
      Maven Plugin: 2.14 & 2.13

      Since:
      I assume it lasts for at least 3 weeks.
      Until a recent update (didn't receive the detail from our dev team about the bug right after the update so not sure to which it applies)
      I also downgrade to 2.13 with no luck

      When:
      Both upon job creation and job modification

      How to reproduce:
      Create a Maven job and fill the fields "Root POM" and "Goals and Options" in Build with random (but valid ...) values
      The matching values in the config.xml are not created

      How to counterpass this:
      Edit the config.xml file via SSH and restart Jenkins so it re-parse the file

        1. Thread dump [Jenkins].html
          77 kB
          Francois Aichelbaum
        2. System Information [Jenkins].html
          50 kB
          Francois Aichelbaum
        3. POST.png
          5 kB
          Francois Aichelbaum

          [JENKINS-39214] "Goals and Options" and "Root POM" not written to config.xml

          Francois Aichelbaum created issue -
          Francois Aichelbaum made changes -
          Rank New: Ranked higher
          Francois Aichelbaum made changes -
          Description Original: Since:
          I assume it lasts for at least 3 weeks.
          Until a recent update (didn't receive the detail from our dev team about the bug right after the update so not sure to which it applies)

          When:
          Both upon job creation and job modification

          How to reproduce:
          Create a job and fill the fields "Root POM" and "Goals and Options" in Build with random (but valid ...) values
          The matching values in the config.xml are not created

          How to counterpass this:
          Edit the config.xml file via SSH and restart Jenkins so it re-parse the file
          New: Since:
          I assume it lasts for at least 3 weeks.
          Until a recent update (didn't receive the detail from our dev team about the bug right after the update so not sure to which it applies)

          When:
          Both upon job creation and job modification

          How to reproduce:
          Create a Maven job and fill the fields "Root POM" and "Goals and Options" in Build with random (but valid ...) values
          The matching values in the config.xml are not created

          How to counterpass this:
          Edit the config.xml file via SSH and restart Jenkins so it re-parse the file
          Francois Aichelbaum made changes -
          Description Original: Since:
          I assume it lasts for at least 3 weeks.
          Until a recent update (didn't receive the detail from our dev team about the bug right after the update so not sure to which it applies)

          When:
          Both upon job creation and job modification

          How to reproduce:
          Create a Maven job and fill the fields "Root POM" and "Goals and Options" in Build with random (but valid ...) values
          The matching values in the config.xml are not created

          How to counterpass this:
          Edit the config.xml file via SSH and restart Jenkins so it re-parse the file
          New: Since:
          I assume it lasts for at least 3 weeks.
          Until a recent update (didn't receive the detail from our dev team about the bug right after the update so not sure to which it applies)
          I also downgrade to 2.13 with no luck

          When:
          Both upon job creation and job modification

          How to reproduce:
          Create a Maven job and fill the fields "Root POM" and "Goals and Options" in Build with random (but valid ...) values
          The matching values in the config.xml are not created

          How to counterpass this:
          Edit the config.xml file via SSH and restart Jenkins so it re-parse the file
          Francois Aichelbaum made changes -
          Environment Original: OS: Ubuntu 14.04
          Jenkins: 2.27 (installed & updated from official APT repo)
          Maven Plugin: 2.14
          New: OS: Ubuntu 14.04
          Jenkins: 2.27 (installed & updated from official APT repo)
          Maven Plugin: 2.14 & 2.13

          Andrew Bayer added a comment -

          Hrrm - I can't reproduce this with a fresh install of Jenkins 2.27 and Maven plugin 2.14 on OS X (just using the war file). Does anything show up in the Jenkins log on the master when you try to save a Maven job with changed goals/root POM?

          Andrew Bayer added a comment - Hrrm - I can't reproduce this with a fresh install of Jenkins 2.27 and Maven plugin 2.14 on OS X (just using the war file). Does anything show up in the Jenkins log on the master when you try to save a Maven job with changed goals/root POM?

          Just "{}" upon Save

          Francois Aichelbaum added a comment - Just "{}" upon Save

          Andrew Bayer added a comment - - edited

          In jenkins.log? Hrm.

          Andrew Bayer added a comment - - edited In jenkins.log? Hrm.

          Sadly, yes.
          I got the exact same reaction

          Francois Aichelbaum added a comment - Sadly, yes. I got the exact same reaction
          Francois Aichelbaum made changes -
          Attachment New: POST.png [ 34492 ]

            aheritier Arnaud Héritier
            faichelbaum Francois Aichelbaum
            Votes:
            6 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated:
              Resolved: