For anyone else dealing with this issue, I found the solution. I recently moved to using folders in Jenkins 2.x, and it's necessary to specify the folder name in the downstream job text field for the post-build action, but only for the manual trigger. I found this info here: https://issues.jenkins-ci.org/browse/JENKINS-34099.
On Thursday, July 14, 2016 at 4:04:30 PM UTC-7, Guy Knights wrote: > > In Jenkins 2.7.1 with build-pipeline plugin 1.5.3.1 I'm trying to set a > manual downstream trigger for a job using the "Build other projects (manual > step)" post-build action, but it can't seem to find any projects in the > same folder, and if I type the name in manually it gives me a "No such > project" error like so: > > *No such project ‘CLIENT - Deploy to production’. Did you mean ‘CLIENT - > Deploy to production?* > > As you can see, the name it suggests is the same as the name it says it > can't find, which is perplexing. I try copying the name it suggests into > the downstream project names box, but it still gives me the same error. > > If I use the "Trigger parameterized build on other projects" post-build > action instead, it finds all the projects fine and I can use this method, > but of course it executes without manual intervention, which is not what > I'm after. I used to run Jenkins 1.65 and this worked fine, so I'm > wondering if it's a bug related to this new Jenkins version. Does anyone > know how to fix this? > > Thanks, > Guy > > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/3e490061-9e7d-4b4d-aaa5-20b6ca515791%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
