"Error:no Such job '" Problem resolution occurs when Jenkins uses Jenkins-cli.jar to make a remote call (Windows)

The most recommended solution on the Web is to log in with SSH key, but I find Linux very easy to implement, but Windows doesn't know where to set it.

Original: https://issues.jenkins-ci.org/browse/JENKINS-12543

Foreign reference: Http://stackoverflow.com/questions/21609589/jenkins-cli-build-on-cloudbees-no-such-job

Domestic reference: http://www.lai18.com/content/6214326.html

Look at the article is basically a very classic solution to the idea.

The solution to go back to Windows is to add readable permissions to the job on the permissions of anonymous users, but officials do not advocate such practices, especially Jenkins, which is deployed to the public network, and faces security issues.

I suggest: when you build Jenkins, run Master on Linux, and then build dotnet projects with slave, so you can save a lot of things on subsequent configurations.

The following are the configuration steps in Windows:

"System Management", "Configure Global Security", "Access Control", "Authorization Policy":

Note: I am here administrator users are self-established, according to the actual situation to increase

It is highly discouraged to do so.

"Error:no Such job '" Problem resolution occurs when Jenkins uses Jenkins-cli.jar to make a remote call (Windows)