-
Improvement
-
Resolution: Fixed
-
Major
-
None
-
Jenkins 1.460 on Debian Squeeze
Right now, every call on the buildWithParameters URL will always redirect to the job page on success. If this API is queried through an Ajax call, it should return a JSON output of the current job instead. This can easily be detected based on the Content-Type http header sent by the client.
This is useful for example if one wants to trigger a parametrized build from jQuery, and parse the result. Right now, jQuery will always get back the HTML page of the job, which makes it hard to do any error handling.
- is related to
-
JENKINS-22865 buildWithParameters doesn't redirect to the build page
-
- Reopened
-
[JENKINS-13546] buildWithParameters: return a JSON string when client request it through content-type header
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Resolution | Original: Fixed [ 1 ] | |
Status | Original: Resolved [ 5 ] | New: Reopened [ 4 ] |
Status | Original: Reopened [ 4 ] | New: In Progress [ 3 ] |
Assignee | New: Bertrand Roussel [ corfr ] |
Code changed in jenkins
User: Reynald Borer
Path:
changelog.html
core/src/main/java/hudson/model/ParametersDefinitionProperty.java
http://jenkins-ci.org/commit/jenkins/1409fdff1955581b91904d73781054a63f1d6f85
Log:
[FIXED JENKINS-13546]: return a JSON string when client request it through content-type header
When a client uses the buildWithParameters API and request a json output, return the job definition as a json string instead of doing a redirect on the job page.