[JIRA] (JENKINS-37471) Build Pipeline Plugin Maunal Trigger not working in Folders
Title: Message Title Mark Bidewell closed an issue as Not A Defect Jenkins / JENKINS-37471 Build Pipeline Plugin Maunal Trigger not working in Folders Change By: Mark Bidewell Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37471) Build Pipeline Plugin Maunal Trigger not working in Folders
Title: Message Title Mark Bidewell resolved as Not A Defect This issue is caused by not specifying the full project name (including folder path). Jenkins / JENKINS-37471 Build Pipeline Plugin Maunal Trigger not working in Folders Change By: Mark Bidewell Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-37471) Build Pipeline Plugin Maunal Trigger not working in Folders
Title: Message Title Mark Bidewell updated an issue Jenkins / JENKINS-37471 Build Pipeline Plugin Maunal Trigger not working in Folders Change By: Mark Bidewell I am trying to organize jobs in jenkins using the folders plugin. When trying to manually trigger a build in the pipeline between two jobs in the folder I receive an exception similar to the following: Aug 16, 2016 4:52:51 PM au.com.centrumsystems.hudson.plugin.buildpipeline.BuildPipelineView triggerBuild SEVERE: No upstream trigger found for this projectAccelerated Client Experience » service-ace-tracker-api-devacetrack01-deployAug 16, 2016 4: 50 52 : 17 51 PM se org . diabol kohsuke . jenkins stapler . pipeline.DeliveryPipelineView triggerManual HttpResponseRenderer$Default handleJavaScriptProxyMethodCall WARNING: Could not trigger manual build ACE call to / service-ace-tracker-api-devacetrack01-deploy for upstream ACE $stapler / service bound/6c2ef2bd - ace 4b56 - tracker 4307 - api 9b6b - ci id: 5 8407f34bfbf1/triggerManualBuild failedjava . Did you mean to specify lang.IllegalStateException: No upstream trigger found for this projectAccelerated Client Experience » service-ace-tracker-api-devacetrack01-deploy ? se.diabol.jenkins.pipeline.trigger.TriggerException: Could not trigger at se au . diabol com . jenkins centrumsystems . pipeline hudson . trigger plugin . BPPManualTrigger buildpipeline . triggerManual BuildPipelineView.triggerBuild ( BPPManualTrigger BuildPipelineView .java: 38 496 ) at se au . diabol com . jenkins centrumsystems . pipeline hudson . DeliveryPipelineView plugin . triggerManual buildpipeline.BuildPipelineView.triggerManualBuild ( DeliveryPipelineView BuildPipelineView .java: 419 405 ) at se sun . diabol reflect . jenkins NativeMethodAccessorImpl . pipeline.PipelineApi.doManualStep invoke0 ( PipelineApi.java:50 Native Method ) at sun.reflect. GeneratedMethodAccessor2261 NativeMethodAccessorImpl .invoke( Unknown Source NativeMethodAccessorImpl.java:62 ) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:320) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:163) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$ 1 _javascript_ProxyMethodDispatcher .doDispatch(MetaClass.java: 124 474 ) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$ 3 11 . doDispatch(MetaClass.java:196) at org.kohsuke.stapler.NameBasedDispatcher. dispatch( NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler. MetaClass $5 . doDispatch(MetaClass. java: 233 380 ) at org.kohsuke.stapler.
[JIRA] (JENKINS-37471) Build Pipeline Plugin Maunal Trigger not working in Folders
Title: Message Title Mark Bidewell created an issue Jenkins / JENKINS-37471 Build Pipeline Plugin Maunal Trigger not working in Folders Issue Type: Bug Assignee: Unassigned Components: build-pipeline-plugin Created: 2016/Aug/17 2:12 PM Environment: Jenkins 1.651.3 build-pipeline-plugin 1.5.3.1 Priority: Critical Reporter: Mark Bidewell I am trying to organize jobs in jenkins using the folders plugin. When trying to manually trigger a build in the pipeline between two jobs in the folder I receive an exception similar to the following: SEVERE: No upstream trigger found for this projectAccelerated Client Experience » service-ace-tracker-api-devacetrack01-deploy Aug 16, 2016 4:50:17 PM se.diabol.jenkins.pipeline.DeliveryPipelineView triggerManual WARNING: Could not trigger manual build ACE/service-ace-tracker-api-devacetrack01-deploy for upstream ACE/service-ace-tracker-api-ci id: 5. Did you mean to specify service-ace-tracker-api-devacetrack01-deploy? se.diabol.jenkins.pipeline.trigger.TriggerException: Could not trigger at se.diabol.jenkins.pipeline.trigger.BPPManualTrigger.triggerManual(BPPManualTrigger.java:38) at se.diabol.jenkins.pipeline.DeliveryPipelineView.triggerManual(DeliveryPipelineView.java:419) at se.diabol.jenkins.pipeline.PipelineApi.doManualStep(PipelineApi.java:50) at sun.reflect.GeneratedMethodAccessor2261.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:320) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:163) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:124)
