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

[pcleary00@gmail.com (JIRA)]

Paul Cleary created an issue

Jenkins / JENKINS-37701 Manual trigger not running in build pipeline Issue Type: Bug Assignee: Unassigned Components: build-pipeline-plugin Created: 2016/Aug/25 9:39 PM Environment: Jenkins 2.19, Build Pipeline Plugin 1.5.3.1 Priority: Minor Reporter: Paul Cleary 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) Add Comment

This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)

[pcleary00@gmail.com (JIRA)]

Paul Cleary updated an issue

Jenkins / JENKINS-37701 Manual trigger not running in build pipeline

Change By: Paul Cleary Environment: Jenkins 2. 19 8 , Build Pipeline Plugin 1.5.3.1

Add Comment

[john_lozano2003@yahoo.com (JIRA)]

John Lozano commented on JENKINS-37701

Re: Manual trigger not running in build pipeline Same issue here with jenkins 2.21 and Build Pipeline 1.5.4

Add Comment

[derekxlu@gmail.com (JIRA)]

DEREK LU commented on JENKINS-37701

Re: Manual trigger not running in build pipeline

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

Add Comment

[pcleary00@gmail.com (JIRA)]

Paul Cleary commented on JENKINS-37701

Re: Manual trigger not running in build pipeline

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

Add Comment

[mikewitters@java.net (JIRA)]

mikewitters commented on JENKINS-37701

Re: Manual trigger not running in build pipeline

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

Add Comment

[alvizu@gmail.com (JIRA)]

Dan Alvizu commented on JENKINS-37701

Re: Manual trigger not running in build pipeline

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

Add Comment

[kalyankix@gmail.com (JIRA)]

Kalyan Koduru commented on JENKINS-37701

Re: Manual trigger not running in build pipeline

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.

Add Comment

[rdsubhas@gmail.com (JIRA)]

Subhas Dandapani commented on JENKINS-37701

Re: Manual trigger not running in build pipeline

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 wrong, it doesn't complain but silently fails when triggering.

Add Comment

[derekxlu@gmail.com (JIRA)]

DEREK LU commented on JENKINS-37701

Re: Manual trigger not running in build pipeline

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>

Add Comment

[rdsubhas@gmail.com (JIRA)]

Subhas Dandapani edited a comment on JENKINS-37701

Re: Manual trigger not running in build pipeline

[~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.

Add Comment