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

          Karsten Günther created issue -
          Karsten Günther made changes -
          Summary Original: Job generator config loses "Costom Workspace" everytime the configuration is edited New: Job generator config loses "Custom Workspace" everytime the configuration is edited

          Daniel Beck added a comment -

          Definitely not a blocker.

          Daniel Beck added a comment - Definitely not a blocker.
          Daniel Beck made changes -
          Priority Original: Blocker [ 1 ] New: Minor [ 4 ]

          Daniel Beck added a comment -

          Could be caused by JENKINS-25221. Would be interesting to know exactly which Jenkins release introduced the problem.

          Daniel Beck added a comment - Could be caused by JENKINS-25221 . Would be interesting to know exactly which Jenkins release introduced the problem.
          Jesse Glick made changes -
          Component/s Original: core [ 15593 ]
          Jesse Glick made changes -
          Link New: This issue is related to JENKINS-23390 [ JENKINS-23390 ]

          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.

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

              Created:
              Updated: