On 08/25/2015 05:31 AM, Daniel Beck wrote:
On 25.08.2015, at 09:26, Alan Evangelista <ala...@linux.vnet.ibm.com> wrote:
I tried to use the idea proposed in
https://issues.jenkins-ci.org/browse/JENKINS-12827 , but Location header in
HTTP response always point to job URL
Did you follow the instructions on /job/<job name>/api to start the build?
There are other suggestions out there how to do this (JSON parameter) and aren't
really 'API' -- you're just imitating browser behavior.
I followed the instructions on
https://wiki.jenkins-ci.org/display/JENKINS/Remote+access+API, which
uses the /job/<job_name>/build URL and the JSON parameter. I thought
this was the official Jenkins REST API documentation?
Accessing /job/<job name>/api instructions at my Jenkins server, I read:
"
Perform a build
To programmatically schedule a new build, post to this URL
(<server_url>/job/<job_name>/build). If the build has parameters, post
to this URL (<server_url>/job/<job_name>/buildWithParameters) and
provide the parameters as form data.
"
I'm confused. Should I use /buildWithParameters REST call instead of /build?
--
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/55DC745B.9090209%40linux.vnet.ibm.com.
For more options, visit https://groups.google.com/d/optout.
