The content of the "custom workspace" changes when job configuration is saved or new job is created:

      For example:

      /ci/test

      changes to

      {"directory":["/ci/test",""]}

          [JENKINS-25221] Content of "Custom Workspace" changes in v1.585

          Matthew Moore added a comment -

          FYI, for those people rolling back their Jenkins version, you might consider 1.580, which was chosen to be the basis for the next LTS release line.

          Matthew Moore added a comment - FYI, for those people rolling back their Jenkins version, you might consider 1.580, which was chosen to be the basis for the next LTS release line.

          Daniel Beck added a comment -

          FYI, for those people rolling back their Jenkins version, you might consider 1.580, which was chosen to be the basis for the next LTS release line.

          Uh, yeah, the basis. With several fixes applied, plus all the security fixes from 1.583.


          The Jenkins changelog contains a community rating feature. Click 'Community ratings' link, and you'll see how others like a release, and what issues they experience, and can leave your own rating. This may help selecting a version to up/downgrade to. (I'd probably go with 1.584 instead, based on that feedback and skimming over the code changes)

          Daniel Beck added a comment - FYI, for those people rolling back their Jenkins version, you might consider 1.580, which was chosen to be the basis for the next LTS release line. Uh, yeah, the basis. With several fixes applied , plus all the security fixes from 1.583. The Jenkins changelog contains a community rating feature. Click 'Community ratings' link, and you'll see how others like a release, and what issues they experience, and can leave your own rating. This may help selecting a version to up/downgrade to. (I'd probably go with 1.584 instead, based on that feedback and skimming over the code changes)

          Goffredo Marocchi added a comment - - edited

          This is a major blocker for me too... incredibly annoying bug .

          Goffredo Marocchi added a comment - - edited This is a major blocker for me too... incredibly annoying bug .

          Sion O'Connor added a comment - - edited

          Aye,

          Ive gone back to 1.584 and all looking ok now - you just need to go through all jobs and reset the custom workspace - really annoying if you got loads of jobs, but you can grep/sed through config xmls and then reload from disk.

          Siôn

          Sion O'Connor added a comment - - edited Aye, Ive gone back to 1.584 and all looking ok now - you just need to go through all jobs and reset the custom workspace - really annoying if you got loads of jobs, but you can grep/sed through config xmls and then reload from disk. Siôn

          Matthew Moore added a comment -

          FYI, this should only affect jobs that you have explicitly saved since the core upgrade, as it only affects round-tripping through the Web Interface.

          Please LMK if that isn't consistent with what you are seeing.

          Matthew Moore added a comment - FYI, this should only affect jobs that you have explicitly saved since the core upgrade, as it only affects round-tripping through the Web Interface. Please LMK if that isn't consistent with what you are seeing.

          I've also observed this problem on Debian 7.7 with versions v.1585 and v.1586.
          No problem with v.1584.

          For me the problem is easily reproducible:

          • Create a multi-configuration project
          • Set "Use custom workspace" in Advanced Project Options (I've used "xxx" for testing)
          • Save the project
          • If you reopen the project configuration and look at the custom workspace setting it contains ' {"directory":["xxx",""]}

            '

          Bernhard Miklautz added a comment - I've also observed this problem on Debian 7.7 with versions v.1585 and v.1586. No problem with v.1584. For me the problem is easily reproducible: Create a multi-configuration project Set "Use custom workspace" in Advanced Project Options (I've used "xxx" for testing) Save the project If you reopen the project configuration and look at the custom workspace setting it contains ' {"directory":["xxx",""]} '

          Matthew Moore added a comment -

          FYI, I have relaxed my prior change that caused this: https://github.com/jenkinsci/jenkins/pull/1446

          I tested this locally with MatrixProject, and confirmed I get the proper value for custom workspace.

          Matthew Moore added a comment - FYI, I have relaxed my prior change that caused this: https://github.com/jenkinsci/jenkins/pull/1446 I tested this locally with MatrixProject, and confirmed I get the proper value for custom workspace.

          Code changed in jenkins
          User: Jesse Glick
          Path:
          changelog.html
          http://jenkins-ci.org/commit/jenkins/3880e00190a7432ad6aa53186fdb62154d3218a0
          Log:
          [FIXED JENKINS-25221] Noting merge of #1446.

          Compare: https://github.com/jenkinsci/jenkins/compare/86ea65ab6fe7...3880e00190a7

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Jesse Glick Path: changelog.html http://jenkins-ci.org/commit/jenkins/3880e00190a7432ad6aa53186fdb62154d3218a0 Log: [FIXED JENKINS-25221] Noting merge of #1446. Compare: https://github.com/jenkinsci/jenkins/compare/86ea65ab6fe7...3880e00190a7

          dogfood added a comment -

          Integrated in jenkins_main_trunk #3785
          [FIXED JENKINS-25221] Noting merge of #1446. (Revision 3880e00190a7432ad6aa53186fdb62154d3218a0)

          Result = SUCCESS
          jesse glick : 3880e00190a7432ad6aa53186fdb62154d3218a0
          Files :

          • changelog.html

          dogfood added a comment - Integrated in jenkins_main_trunk #3785 [FIXED JENKINS-25221] Noting merge of #1446. (Revision 3880e00190a7432ad6aa53186fdb62154d3218a0) Result = SUCCESS jesse glick : 3880e00190a7432ad6aa53186fdb62154d3218a0 Files : changelog.html

          Moshe Zvi added a comment -

          I'm on 1.588, and in a Maven project I don't see the custom workspace option at all...

          Moshe Zvi added a comment - I'm on 1.588, and in a Maven project I don't see the custom workspace option at all...

            mattmoor Matthew Moore
            skhushalani Sagar Khushalani
            Votes:
            5 Vote for this issue
            Watchers:
            14 Start watching this issue

              Created:
              Updated:
              Resolved: