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

build flow plugin does not properly initialize workspace but supports options (SCM) that require a workspace

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • build-flow-plugin
    • None

      The build flow job type does not initialize the project's workspace. However, this project supports options, like SCM, that require a workspace to be initialized. This means:

      1. build-flow projects cannot use SCM
        • build-flow projects cannot be triggered by SCM changes if that trigger requires a workspace. Due to JENKINS-20767 all Git triggered projects currently require a workspace.
      2. build-flow projects cannot use any post-build action that assumes a workspace. EG: archive artifacts

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

          [JENKINS-20843] build flow plugin does not properly initialize workspace but supports options (SCM) that require a workspace

          Corey O'Connor created issue -
          Corey O'Connor made changes -
          Description Original: The build flow job type does not initialize the project's workspace. However, this project supports options, like SCM, that require a workspace to be initialized. This means:

          # build-flow projects cannot use SCM
          #* build-flow projects cannot be triggered by SCM changes if that trigger requires a workspace. Due to JENKINS-20767 all Git triggered projects currently require a workspace.
          # build-flow projects cannot use any post-build action that assumes a workspace. EG: archive artifacts           		New: The build flow job type does not initialize the project's workspace. However, this project supports options, like SCM, that require a workspace to be initialized. This means:

          # build-flow projects cannot use SCM
          #* build-flow projects cannot be triggered by SCM changes if that trigger requires a workspace. Due to JENKINS-20767 all Git triggered projects currently require a workspace.
          # build-flow projects cannot use any post-build action that assumes a workspace. EG: archive artifacts

          commit that introduced issue: https://github.com/jenkinsci/build-flow-plugin/commit/444097d65ecb97c92005b3acd63db8e03bdeb6a3
          Corey O'Connor made changes -
          Link New: This issue is related to JENKINS-20767 [ JENKINS-20767 ]

          Nicolas De Loof added a comment -

          I don't think there's a way to filter build step to require a workspace.
          Archiving artifact for a flow don't make sense, only jobs triggered by artifact have built artifacts to be archived.

          Nicolas De Loof added a comment - I don't think there's a way to filter build step to require a workspace. Archiving artifact for a flow don't make sense, only jobs triggered by artifact have built artifacts to be archived.

          Corey O'Connor added a comment -

          I'd expect the requirements of a build steps should be something jenkins would filter on.

          As for archive artifact: That "archive artifacts" doesn't make sense for a build flow job is an example of the issue. If archiving artifacts does not make sense then the step should not be selectable in the UI.

          Anyways, sounds like properly resolving this issue requires changes to jenkins core.

          Corey O'Connor added a comment - I'd expect the requirements of a build steps should be something jenkins would filter on. As for archive artifact: That "archive artifacts" doesn't make sense for a build flow job is an example of the issue. If archiving artifacts does not make sense then the step should not be selectable in the UI. Anyways, sounds like properly resolving this issue requires changes to jenkins core.
          Dylan Meissner made changes -
          Link New: This issue is related to JENKINS-22725 [ JENKINS-22725 ]

          Damien Nozay added a comment -

          build-flow v. 0.12 can now use a workspace back again.
          https://github.com/jenkinsci/build-flow-plugin/commit/00b7ad56eca41eebcfd19bd3e54de0ace66ae0be

          Corey, could you please verify you are now able to use it as you intended?

          Damien Nozay added a comment - build-flow v. 0.12 can now use a workspace back again. https://github.com/jenkinsci/build-flow-plugin/commit/00b7ad56eca41eebcfd19bd3e54de0ace66ae0be Corey, could you please verify you are now able to use it as you intended?

          Philipp Strobel added a comment -

          build-flow-plugin 0.17 does not prepare the workspace after SCM checkout. The workspace stays empty. I use the SCM to check for changes on the SCM and to trigger a new Job-Run. However, since the workspace is always empty, each time the SCM is checked for changes it will trigger a new Job-Run.

          Philipp Strobel added a comment - build-flow-plugin 0.17 does not prepare the workspace after SCM checkout. The workspace stays empty. I use the SCM to check for changes on the SCM and to trigger a new Job-Run. However, since the workspace is always empty, each time the SCM is checked for changes it will trigger a new Job-Run.
          Baptiste Mathus made changes -
          Assignee Original: Nicolas De Loof [ ndeloof ] New: Damien Nozay [ dnozay ]
          Damien Nozay made changes -
          Assignee Original: Damien Nozay [ dnozay ]

            Unassigned Unassigned
            coreyoconnor Corey O'Connor
            Votes:
            3 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated: