• Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • build-pipeline-plugin
    • None
    • Jenkins 2.8, Build Pipeline Plugin 1.5.3.1

      We are using Folders to manage our build jobs.

      The folder structure looks like:

      Denis/

      So, it is only one level deep.

      I am trying to setup a build pipeline. I used the Post Build Action of a "Build other projects (manual)" step.

      I set the name of the project to use the folder structure:

      /Denis/job-name

      Everything appears fine in the Build Pipeline View, but when I click on the "manual trigger" icon, it doesn't run.

      Inspecting the Jenkins log I am seeing:

      call to /$stapler/bound/02d15e0b-6aab-4b6d-9c5b-9b7d4ea028f4/triggerManualBuild failed
      java.lang.IllegalStateException: No upstream trigger found for this projectDenis ยป denis-publish-portal
      	at au.com.centrumsystems.hudson.plugin.buildpipeline.BuildPipelineView.triggerBuild(BuildPipelineView.java:496)
      	at au.com.centrumsystems.hudson.plugin.buildpipeline.BuildPipelineView.triggerManualBuild(BuildPipelineView.java:405)
      	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      

          [JENKINS-37701] Manual trigger not running in build pipeline

          John Lozano added a comment -

          Same issue here with jenkins 2.21 and Build Pipeline 1.5.4

          John Lozano added a comment - Same issue here with jenkins 2.21 and Build Pipeline 1.5.4

          DEREK LU added a comment -

          I'm doing the same thing with 2.7.2 with build pipeline plugin 1.5.4 and it works fine.
          In Build Other Projects (manual step) specify Downstream Project Names without the leading /, for example
          Project/BuildJobs/Manual_Test
          if you do Denis/job-name it should work

          DEREK LU added a comment - I'm doing the same thing with 2.7.2 with build pipeline plugin 1.5.4 and it works fine. In Build Other Projects (manual step) specify Downstream Project Names without the leading /, for example Project/BuildJobs/Manual_Test if you do Denis/job-name it should work

          Paul Cleary added a comment -

          I still have the issue with version 2.8 with build pipeline plugin 1.5.4

          Paul Cleary added a comment - I still have the issue with version 2.8 with build pipeline plugin 1.5.4

          mikewitters added a comment -

          Any movement on this or does anyone have a work around? We're still getting this problem with no known work-around on Jenkins (Cloudbees) version 2.7.20.2 and build plugin version 1.5.6

          Thanks,
          Mike

          mikewitters added a comment - Any movement on this or does anyone have a work around? We're still getting this problem with no known work-around on Jenkins (Cloudbees) version 2.7.20.2 and build plugin version 1.5.6 Thanks, Mike

          Dan Alvizu added a comment -

          See DEREK LU's comment for a work-around:

          > In Build Other Projects (manual step) specify Downstream Project Names without the leading /, for example
          Project/BuildJobs/Manual_Test

          Dan Alvizu added a comment - See DEREK LU's comment for a work-around: > In Build Other Projects (manual step) specify Downstream Project Names without the leading /, for example Project/BuildJobs/Manual_Test

          Kalyan Koduru added a comment -

          We ran into the same issue, and had to move the jobs, and pipeline from folders into "global view" to get the manual triggers work. Delivery Pipeline has the same issue as it uses Build Pipeline Plugin.

          Kalyan Koduru added a comment - We ran into the same issue, and had to move the jobs, and pipeline from folders into "global view" to get the manual triggers work. Delivery Pipeline has the same issue as it uses Build Pipeline Plugin.

          Subhas Dandapani added a comment - - edited

          kalyankix We finally found the problem and its really simple.

          Case mismatch when specifying downstream trigger names, really As long as you specify the exact upper/lower case characters (of the whole job path, including folder names) - its fine. But if you specify the case wrong, it doesn't complain in the UI but silently fails when triggering.

          Subhas Dandapani added a comment - - edited kalyankix We finally found the problem and its really simple. Case mismatch when specifying downstream trigger names, really As long as you specify the exact upper/lower case characters (of the whole job path, including folder names) - its fine. But if you specify the case wrong, it doesn't complain in the UI but silently fails when triggering.

          DEREK LU added a comment -

          Good to hear that you have it working. It is the Full project name that you can directly copy from the reference job. Once you open the job the Full name (with path) is displayed under the Project <JOB NAME>

          DEREK LU added a comment - Good to hear that you have it working. It is the Full project name that you can directly copy from the reference job. Once you open the job the Full name (with path) is displayed under the Project <JOB NAME>

          I'm getting the same problem.

          Stacktrace: https://gist.github.com/robsonpeixoto/3922723719d3748b34d8c8d408afdd5e

          Build Pipeline Plugin: 1.5.7.1

          Jenkins: 2.60.2

          Job DSL: 1.64 

           

          Robson Peixoto added a comment - I'm getting the same problem. Stacktrace:  https://gist.github.com/robsonpeixoto/3922723719d3748b34d8c8d408afdd5e Build Pipeline Plugin: 1.5.7.1 Jenkins: 2.60.2 Job DSL: 1.64   

          James Chao added a comment -

          Thanks derekxlu that workaround totally worked for me.

          James Chao added a comment - Thanks derekxlu that workaround totally worked for me.

            Unassigned Unassigned
            pcleary Paul Cleary
            Votes:
            2 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated: