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

build.workspace always null

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not A Defect
    • Icon: Minor Minor
    • build-flow-plugin
    • None
    • Jenkins ver. 1.560

      The following simple statement always prints null.

      out.println build.workspace

      This began happening to existing build-flow jobs when recently upgrading to the build-flow plugin to 0.11, and is reproducible when creating new build-flow jobs as well. This functionality is important when the build-flow job is creating artifacts.

        1. flyweight.png
          flyweight.png
          67 kB

          [JENKINS-22725] build.workspace always null

          Damien Nozay added a comment -

          There was a commit in version 0.11 that removed the workspace.

          https://github.com/jenkinsci/build-flow-plugin/commit/444097d65ecb97c92005b3acd63db8e03bdeb6a3

          You can get the 0.10 version of the plugin here:
          http://updates.jenkins-ci.org/download/plugins/build-flow-plugin/0.10/build-flow-plugin.hpi

          Damien Nozay added a comment - There was a commit in version 0.11 that removed the workspace. https://github.com/jenkinsci/build-flow-plugin/commit/444097d65ecb97c92005b3acd63db8e03bdeb6a3 You can get the 0.10 version of the plugin here: http://updates.jenkins-ci.org/download/plugins/build-flow-plugin/0.10/build-flow-plugin.hpi

          Dylan Meissner added a comment -

          I see this was intentional. While I think it's a sad decision to remove this useful functionality, the remaining issue is that the plugin documentation still shows this as a feature in one of its examples.

          Dylan Meissner added a comment - I see this was intentional. While I think it's a sad decision to remove this useful functionality, the remaining issue is that the plugin documentation still shows this as a feature in one of its examples.

          Dylan Meissner added a comment - - edited

          Added a screenshot taken from the build-flow plugin page referencing a feature that was yanked between 0.10 and 0.11.

          Dylan Meissner added a comment - - edited Added a screenshot taken from the build-flow plugin page referencing a feature that was yanked between 0.10 and 0.11.

          Daniel Beck added a comment -

          This is a documented, deliberate change that has been announced in March 2013 on the mailing list, and discussed to death since.

          Note that Nicolas, the plugin maintainer so far, also wrote he gave up on the plugin. Given that there will probably not be a lot of activity in the near future, just downgrade the plugin to a version that still had a workspace (and maybe plan for a replacement).

          Daniel Beck added a comment - This is a documented, deliberate change that has been announced in March 2013 on the mailing list, and discussed to death since. Note that Nicolas, the plugin maintainer so far, also wrote he gave up on the plugin . Given that there will probably not be a lot of activity in the near future, just downgrade the plugin to a version that still had a workspace (and maybe plan for a replacement).

          Mark Hudson added a comment -

          The wiki page announces the deprecated status of this plugin at https://wiki.jenkins-ci.org/display/JENKINS/Build+Flow+Plugin
          Similar Goovy-based DSL is officially supported in https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Plugin

          Mark Hudson added a comment - The wiki page announces the deprecated status of this plugin at https://wiki.jenkins-ci.org/display/JENKINS/Build+Flow+Plugin Similar Goovy-based DSL is officially supported in https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Plugin

            ndeloof Nicolas De Loof
            dylanmei Dylan Meissner
            Votes:
            3 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: