More progress, the error below can be resolved by passing --user
"username:password" to curl. i.e.
curl -X POST http://jenkins.ourdomain.com/job/somejob/build?token=testtoken
--user
"username:password"
However, the issue I have now is I can only get a job to work by specifying
an existing nod
I think I will partially answer my own question:
I found this:
https://wiki.jenkins-ci.org/display/JENKINS/Remote+access+API
And so I edited one of the jobs and clicked on the option Trigger Builds
remotely, and then entered an Authentication token, and ran the job from
the remote server via:
c
I've googled around, and I haven't been able to locate much on what we'd
like to do.
We have some cloud based servers. We use jenkins to manage the
build/deploy processes to update code to these servers.
We are testing some auto-scaling features, so the cloud will automatically
launch new web
