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

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

          Olivier Lamy added a comment -

          Well that's weird.
          I had a quick look and cannot reproduce with hpi:run.
          I will have a try later with a real jenkins distribution (and I guess an upgrade of the plugin as well not with a fresh new install).
          There is no real changes related which is even worst.

          Olivier Lamy added a comment - Well that's weird. I had a quick look and cannot reproduce with hpi:run. I will have a try later with a real jenkins distribution (and I guess an upgrade of the plugin as well not with a fresh new install). There is no real changes related which is even worst.

          Jenkins 2.27 was a crappy version danielbeck due to stapler updates ? like 2.28 and 2.29 ?
          Thus it may be related to this ?
          But if abedwards and mariem_baccar have the issue on 2.19.x it is more annoying.
          I don't see also on my side a change in the UI or code part to justify that bug.
          For all people having this issue, can you tell us exactly which parameters you are setting in your job ?
          Maybe it is a side effect with another parameter/plugin.
          Also if you could share some samples of corrupted config.xml files it might help to reproduce

          Arnaud Héritier added a comment - Jenkins 2.27 was a crappy version danielbeck due to stapler updates ? like 2.28 and 2.29 ? Thus it may be related to this ? But if abedwards and mariem_baccar have the issue on 2.19.x it is more annoying. I don't see also on my side a change in the UI or code part to justify that bug. For all people having this issue, can you tell us exactly which parameters you are setting in your job ? Maybe it is a side effect with another parameter/plugin. Also if you could share some samples of corrupted config.xml files it might help to reproduce

          Hi Arnaud,

          on my side, it has nothing related to the other params as even if I create a brand new project and fill up only those two params, I'll have the issue.
          You have as an early comment the POST request sent by the UI : as you can see, both params are called several times and the first time is with empty values

          You also have my config details as attachment to this ticket.

          Thanks

          Francois Aichelbaum added a comment - Hi Arnaud, on my side, it has nothing related to the other params as even if I create a brand new project and fill up only those two params, I'll have the issue. You have as an early comment the POST request sent by the UI : as you can see, both params are called several times and the first time is with empty values You also have my config details as attachment to this ticket. Thanks

          Adam added a comment -

          aheritier I can try again later tonight, but I was also able to reproduce the issue using the docker build, therefore I would say it's safe to say it's not related to my install. Putting any value in the maven goals would result in the issue of not saving the values entered.

          Adam added a comment - aheritier I can try again later tonight, but I was also able to reproduce the issue using the docker build, therefore I would say it's safe to say it's not related to my install. Putting any value in the maven goals would result in the issue of not saving the values entered.

          Adam added a comment -

          faichelbaum hmm.. I just tried again, both in docker as well as my regular install and all seems working now. be curious if yours is fixed now too. wondering if maybe there was a plugin update that I did which fixed it.

          Adam added a comment - faichelbaum hmm.. I just tried again, both in docker as well as my regular install and all seems working now. be curious if yours is fixed now too. wondering if maybe there was a plugin update that I did which fixed it.

          Hi abedwards I'm fully up to date but still no luck on my side. Did you change anything else ?

          Francois Aichelbaum added a comment - Hi abedwards I'm fully up to date but still no luck on my side. Did you change anything else ?

          Could be related with JENKINS-39078 if you have Docker Slave Plugin installed

          Ivan Fernandez Calvo added a comment - Could be related with JENKINS-39078 if you have Docker Slave Plugin installed

          ifernandezcalvo thanks ! that was it
          I removed the plugin (unused and version 1.0.5) and it fixed it !

          Francois Aichelbaum added a comment - ifernandezcalvo thanks ! that was it I removed the plugin (unused and version 1.0.5) and it fixed it !

          mariem baccar added a comment -

          mariem baccar added a comment - This problem is related to JENKINS-39078 : There is a problem in Docker Slave Plugin 1.0.5 (Fix: https://github.com/jenkinsci/docker-slaves-plugin/commit/451929125fd8ff39c6f84c30476c26cccb912140 ). So, you can uninstall this plugin if it's not needed. You must be careful. This plugin is also responsible of many other bugs ( JENKINS-39231 , docker compose fails after scrutation...)

          The version 1.0.6 of Docker Slave Plugin also solves that issue

          Arnaud Héritier added a comment - The version 1.0.6 of Docker Slave Plugin also solves that issue

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

              Created:
              Updated:
              Resolved: