I can successfully run the list-jobs CLI: java -jar /path/to/jenkins-cli.jar -s http://my_server.com:8080/ <http://bronn.ast.lmco.com:8080/> list-jobs
and get a full listing of all the project names on my server: project_A project_B project_C ... But if I try to get one of them: java -jar /path/to/jenkins-cli.jar -s http://my_server.com:8080/ <http://bronn.ast.lmco.com:8080/> get-job project_B ... I get this: No such job 'project_B' <... *get-job's usage information * ...> I'm on 1.563. I get the same behavior inside a Jenkins job as I do with a standalone bash script. [FYI: We're using LDAP authentication, and both my Jenkins job and my standalone bash script have the two CLI commands above preceded by a "login", per the workaround shown in https://issues.jenkins-ci.org/browse/JENKINS-21086. I've also done a reload config from disk, but it didn't help.] Bound to be something simple. What am I missing here? -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
