I have a test job at the root of my Jenkins instance named "CheckBuildQueue". If I invoke the Build method with that jobName, all is well. But if move that job into a folder, say Utilities, hence the name of the jobName becomes "Utilities/CheckBuildQueue"; the Build will always return 404 (not found). I tested this jobName using the Jenkins CLI and it works, so there's a difference in this package I need to do. Does anyone know how I need to form the jobName in order to handle the jobs in nested folders? Thanks.
I have a test job at the root of my Jenkins instance named "CheckBuildQueue". If I invoke the Build method with that jobName, all is well. But if move that job into a folder, say Utilities, hence the name of the jobName becomes "Utilities/CheckBuildQueue"; the Build will always return 404 (not found). I tested this jobName using the Jenkins CLI and it works, so there's a difference in this package I need to do. Does anyone know how I need to form the jobName in order to handle the jobs in nested folders? Thanks.