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

Please add support for Cloudbees folder structure

XMLWordPrintable

      We are using Cloudbees folders. I tried using the Build Pipeline plugin. I'm able to select my job from the drop-down, but the pipeline view does not show any of the downstream jobs, unless I create all the jobs at the base level (not in a folder).

          [JENKINS-14565] Please add support for Cloudbees folder structure

          Shimon Tolts added a comment -

          I am having the same issue, could you please fix this

          Shimon Tolts added a comment - I am having the same issue, could you please fix this

          Andreyev Melo added a comment -

          Even if all jobs where in the same folder?

          Andreyev Melo added a comment - Even if all jobs where in the same folder?

          Billy Foss added a comment -

          We are seeing the following issue.
          We have a job in a folder. For the "promote" step we want to copy the artifact from this job and deploy it to Artifactory.

          Jobs outside the Cloudbees folders work fine, but Jobs that are inside a "Folder" get the following error trying to find the project to copy from.

          Promoting FeatureBranches . FB0009 . DataProcessingModules #5
          Unable to find project for artifact copy: DataProcessingModules
          This may be due to incorrect project name or permission settings; see help for project name in job configuration.
          failed build hudson.plugins.copyartifact.CopyArtifact@45ddd0c7 SUCCESS

          Billy Foss added a comment - We are seeing the following issue. We have a job in a folder. For the "promote" step we want to copy the artifact from this job and deploy it to Artifactory. Jobs outside the Cloudbees folders work fine, but Jobs that are inside a "Folder" get the following error trying to find the project to copy from. Promoting FeatureBranches . FB0009 . DataProcessingModules #5 Unable to find project for artifact copy: DataProcessingModules This may be due to incorrect project name or permission settings; see help for project name in job configuration. failed build hudson.plugins.copyartifact.CopyArtifact@45ddd0c7 SUCCESS

          Billy Foss added a comment -

          FYI,
          I found I could get it to work if I use the path in the job name

          FeatureBranches/FB0009/$PROMOTED_JOB_NAME

          Interesting that $PROMOTED_JOB_NAME does not include the full path, but $JOB_NAME does. It resolved to FeatureBranches/FB0009/DataProcessingModules/promoted/Deploy to Artifactory

          Also if I tried to specify a variable defined in the Folder (ie FOLDER=FeatureBranches/FB0009) the variable would not resolve.

          Billy Foss added a comment - FYI, I found I could get it to work if I use the path in the job name FeatureBranches/FB0009/$PROMOTED_JOB_NAME Interesting that $PROMOTED_JOB_NAME does not include the full path, but $JOB_NAME does. It resolved to FeatureBranches/FB0009/DataProcessingModules/promoted/Deploy to Artifactory Also if I tried to specify a variable defined in the Folder (ie FOLDER=FeatureBranches/FB0009) the variable would not resolve.

          Thomas Fürer added a comment -

          I have still the problem to setup a build pipeline with jobs placed in folders. I uses the full path as Billy descibes but I fail.

          Thomas Fürer added a comment - I have still the problem to setup a build pipeline with jobs placed in folders. I uses the full path as Billy descibes but I fail.

          Octavio Martin added a comment -

          I can see my jobs in the pipeline and any chain of automatic jobs works fine, but I cannot execute any manual step in that chain, when button is clicked, it does nothing.

          Octavio Martin added a comment - I can see my jobs in the pipeline and any chain of automatic jobs works fine, but I cannot execute any manual step in that chain, when button is clicked, it does nothing.

          SCM/JIRA link daemon added a comment -

          Code changed in jenkins
          User: Lance Johnston
          Path:
          src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/BuildPipelineView.java
          src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/trigger/BuildPipelineTrigger.java
          http://jenkins-ci.org/commit/build-pipeline-plugin/132e16a21e184e51331080fc9c501a6aba43be69
          Log:
          JENKINS-14565 Cloudbees folder plugin support for manually triggered jobs.

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Lance Johnston Path: src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/BuildPipelineView.java src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/trigger/BuildPipelineTrigger.java http://jenkins-ci.org/commit/build-pipeline-plugin/132e16a21e184e51331080fc9c501a6aba43be69 Log: JENKINS-14565 Cloudbees folder plugin support for manually triggered jobs.

          Kanstantsin Shautsou added a comment -

          As i see commit was released in 1.4.4. Additional fixes are in 1.4.5.
          Release 1.4.5 should appear on mirrors in the next 24h.

          Kanstantsin Shautsou added a comment - As i see commit was released in 1.4.4. Additional fixes are in 1.4.5. Release 1.4.5 should appear on mirrors in the next 24h.

            Unassigned Unassigned
            rmyung Roger Myung
            Votes:
            6 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated:
              Resolved: