I accenditaly reproduce this issue at work.

When using -i for ssh credential, build and some other command doesn't work for job who are not readable by annonymous. (enable-job work)

The workaround is to activate "security based project" and to activate read access to anonymous user.

It must be a visibility issue. CLI see only anonymous job, not jobs seen by account used with -i parameter. On other way, the build start when anonymous have not build rights. So it's only visibility issue.

Is this issue ever going to be resolved? In companies like mine where adding anonymous read access is not an option, and relying on many of the CLI commands, an issue like this limits the things we can do with Jenkins jobs outside the UI. If anyone has a workaround to this, that would be welcome.

The 'build' command does not work either, as the job name cannot be retrieved:
$ java -jar jenkins-cli.jar -s http://localhost:8090 -i ~/.ssh/id_rsa build Project1
–
No such job 'Project1'
java -jar jenkins-cli.jar build args...
Starts a build, and optionally waits for a completion.
(...)
–
And Project1 does exist!

The build command work, but you have to give anonymous read access to your Project1. Then CLI command will see it.
Must be a visibility issue...

Agreed that this is an important issue, I don't want to give anonymous read access just to be able to use the CLI.

Same issue here.

Same here. Anonymous access is not acceptable. Looking for workaround.

I would also like a solution or workaround for this issue.

Having the same issue with --username & --password authentication.

Sad panda for the 1.5 year old ticket

Confirming the workaround - I toggled the Job > Read checkbox for the anonymous user and I can now run builds via the CLI and anonymous users can not see anything when they visit the jenkins URL.

I wrote up the use of the CLI and how to setup this workaround http://starkandwayne.com/articles/2013/04/12/jenkins-builds-from-cli/

wow, thanks a lot dr nic, it solved issues with jenkins-cli in our case,

JENKINS-12543 covers the problems with username/password authentication. I could not reproduce any problems in current trunk with SSH authentication.

Im Using Jenkins-CLI to setup jobs based on an deactivated job template and modify the activation state of the created jobs in a second step. It seems that I run into this issue as the creation of new jobs works as expected but the activation fails:

Calling jenkins api to create job 'eisfair__bcstorage' hudson.security.AccessDeniedException2: anonymous fehlt das Recht 'Job/Configure' 
 	at hudson.security.ACL.checkPermission(ACL.java:54)
 	at hudson.model.AbstractItem.checkPermission(AbstractItem.java:446)
 	...

Why is there "anonymous" used? Username and password is the same as for job creation some milliseconds before!?

Sad story as there are more than 500 jobs handled this way and it is absolutely annoying to do this by hand...

No response to comment asking for updated information in over three months, so resolving as cannot Reproduce.

I'm experiencing this problem. Using CloudBees folders and roles/groups with absolutely no permissions for non-authenticated users.

I can list-job through the folders and see the job. But trying to build it via the cli results in "ERROR: No such job"

It's reproducible!

jswager1 Then please provide enough information so it can be reproduced by someone else, from scratch. I.e. no "I have this Jenkins instance I've worked on for years and it does not work with that".

Apologies, danielbeck, let me add the bare minimum reproduce steps.

1. I installed a fresh Jenkins via it's docker container. The version it had was 1.642.2.
2. Once running and connected, added the Folder Plugin and the Role-based Authorization Strategy (in my production scenario, we're using CloudBees Roles and Groups - but this one will suffice)
3. Enable security via Manage Jenkins -> Global Security: Jenkins own database, allow users to sign-up, Role-Based Strategy.
4. Create yourself as a user and sign in as yourself
5. Under Manage Jenkins -> Manage and Assign Roles: Under Manage Roles, make sure "admin" role has access to everything. Under Assign Roles, remove "Anonymous" group from "admin", add yourself and give access to "admin" role.
6. Back at Jenkins main page, create a Folder (via New Item -> Folder) called "alpha"
7. In Folder "alpha" create a simple Freestyle Job called "test-job", make it do something - whatever. No parameters is easiest.

Now for the command line work (command may be slightly incorrect; typing from memory here) - replace JENKINS_URL and userid as appropriate:

1. At the command line, get the jenkins-cli: curl -o jenkins-cli JENKINS_URL/jnlpJars/jenkins-cli.jar
2. Make it easy - login as you: java -jar jenkins-cli.jar -s JENKINS_URL login --username userid
3. Verify you can see the alpha folder: java -jar jenkins-cli.jar -s JENKINS_URL list-jobs
4. Verify you can see the test-job job: java -jar jenkins-cli.jar -s JENKINS_URL list-jobs alpha
5. Try to run test-job: java -jar jenkins-cli.jar -s JENKINS_URL build alpha/test-job
6. I get the following when I try:

$ java -jar jenkins-cli.jar -s http://192.168.99.100:8080 build "alpha/test-job"
No such job 'alpha/test-job'

jswager1 I don't see any use of the -i switch to use a non-default SSH key in your comment anywhere. How is that related to this issue? Looks like you're just experiencing JENKINS-12543.

Sorry - this is my mistake. This doens't involve the ssh keys, just a normal username/password login. Please close this issue and I'll open a different one.

jswager1 I still maintain you're just seeing JENKINS-12543.