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

Manual trigger not running in build pipeline

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Minor
    • Resolution: Unresolved
    • Component/s: build-pipeline-plugin
    • Labels:
      None
    • Environment:
      Jenkins 2.8, Build Pipeline Plugin 1.5.3.1
    • Similar Issues:

      Description

      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)
      

        Attachments

          Activity

          Hide
          kalyankix 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.

          Show
          kalyankix 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.
          Hide
          fm4zyqnfbbfpim Subhas Dandapani added a comment - - edited

          Kalyan Koduru 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.

          Show
          fm4zyqnfbbfpim Subhas Dandapani added a comment - - edited Kalyan Koduru 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.
          Hide
          derekxlu 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>

          Show
          derekxlu 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>
          Hide
          robsonpeixoto 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 

           

          Show
          robsonpeixoto 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   
          Hide
          jameschao James Chao added a comment -

          Thanks DEREK LU that workaround totally worked for me.

          Show
          jameschao James Chao added a comment - Thanks DEREK LU that workaround totally worked for me.

            People

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

              Dates

              • Created:
                Updated: