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

Job generator config loses "Custom Workspace" everytime the configuration is edited

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • jobgenerator-plugin
    • None
    • Jenkins LTS 1.596.1, Job Generator 1.22, Windows 2008 Server

      I updated my Jenkins LTS installation from version 1.580.3 (LTS) to 1.596.1 (LTS). With both version I used/use the Job Generator plugin 1.22.

      After the update I am facing the problem, that everytime I configure a Job Generator via the web interface, the Job Generator loses its "Custom Workspace" setting.

      This bug is fully reproducible with 1.596.1:
      Just create a Job Generator and configure a Custom Workspace for it. When you save the configuration, the config.xml has the correct element and value. When you configure it again, the value is not loaded into the configuration formular. When hitting "Save", the value disappears from the config.xml.

      It is not reproducible with 1.580.3.

      For me this is a real showstopper as I cannot edit my Job Generators without copying the value of "Custom Workspace" from the config.xml into the formular everytime (my whole project setup depends on it).
      This bug may be related to https://issues.jenkins-ci.org/browse/JENKINS-23390.

          [JENKINS-27219] Job generator config loses "Custom Workspace" everytime the configuration is edited

          Christophe Carpentier added a comment -

          Definitely annoying

          Christophe Carpentier added a comment - Definitely annoying

          Peter Mate added a comment -

          We tried to debug the issue and made a pull request which fixed the issue for us.
          Pull request

          Peter Mate added a comment - We tried to debug the issue and made a pull request which fixed the issue for us. Pull request

          Shannon Kerr added a comment -

          Any chance someone can fix this by taking action on the pull request? This is rather annoying.

          Shannon Kerr added a comment - Any chance someone can fix this by taking action on the pull request? This is rather annoying.

          Karsten Günther added a comment -

          Annoying? This is a show stopper for the job generator plugin.

          Karsten Günther added a comment - Annoying? This is a show stopper for the job generator plugin.

          Shannon Kerr added a comment -

          To me, a show stopper means that the broken plugin has made our CI environment unusable and we've had to revert to an older version or remove the plugin altogether. This particular bug just means that I have to re-add the custom workspace anytime I make a change to the Job Generator project. I noted it on our local Jenkins wiki and have gotten used to having to re-add the custom workspace each time. To me, this is annoying, but still useable.

          Shannon Kerr added a comment - To me, a show stopper means that the broken plugin has made our CI environment unusable and we've had to revert to an older version or remove the plugin altogether. This particular bug just means that I have to re-add the custom workspace anytime I make a change to the Job Generator project. I noted it on our local Jenkins wiki and have gotten used to having to re-add the custom workspace each time. To me, this is annoying, but still useable.

          Bruce Strickland added a comment -

          I hope someone can resolve this issue. It's annoying to have to add the custom path again each time you have to change another value elsewhere in the job. I'm a newbie to Jenkins in windows and still depend on this web interface for now.

          Bruce Strickland added a comment - I hope someone can resolve this issue. It's annoying to have to add the custom path again each time you have to change another value elsewhere in the job. I'm a newbie to Jenkins in windows and still depend on this web interface for now.

          Sławomir Poddębniak added a comment -

          Is there any chance to fix the problem? please
          In the meantime, if someone know any clever workaround

          Sławomir Poddębniak added a comment - Is there any chance to fix the problem? please In the meantime, if someone know any clever workaround

          Peter Mate added a comment -

          Hello,

          well I have created a pull request a year ago which fixed this issue for us. It is still not merged, but we are using the plugin with that change since that time.
          If you build your own plugin with that change, it can fix the issue.
          https://github.com/jenkinsci/jobgenerator-plugin/pull/3

          Peter Mate added a comment - Hello, well I have created a pull request a year ago which fixed this issue for us. It is still not merged, but we are using the plugin with that change since that time. If you build your own plugin with that change, it can fix the issue. https://github.com/jenkinsci/jobgenerator-plugin/pull/3

          Karsten Günther added a comment -

          A workaround for this "not a show stopper"? Replace the plugin with the Job DSL plugin. Fast, reliable and less annoying ...

          Karsten Günther added a comment - A workaround for this "not a show stopper"? Replace the plugin with the Job DSL plugin. Fast, reliable and less annoying ...

          Sławomir Poddębniak added a comment -

          Thank you for these tips!

          Sławomir Poddębniak added a comment - Thank you for these tips!

            Unassigned Unassigned
            xxthunder Karsten Günther
            Votes:
            6 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated: