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