I second this. It would be really nice to see the actual build number
created in the response somewhere when using the api build and
buildWithParameters calls. We can try to figure it out based on the
nextBuildNumber, plus parsing through the queue/api/xml output, but it
is not guaranteed.
I cre
I did it using http parsing, but it is not a good solution.
Also the build can come to queue? and there can be problems with build
number, because it will depend from builds priority in such case.
The best way is to use groovy script for triggering build and getting the
build number then.
2012/2/3
Hello
I have read the doc, and google around, but I have found no solution
so far to the problem of triggering a build via an http call and
getting back a build number (eg json-encoded) instead of a 302
redirect to the page listing project status.
I can call http://jenkins-server/job/my_project/b
