Mixing
Get console output of a jenkins job by sending the build number as a json parameter through api
I'm trying to get the job status by providing the build number as a parameter.
curl -s -S -u "Ashwin":"XXX" "http://XX.XXX.XXX.XX:8080/job/apitest/buildNum/logText/progressiveText?start=0"
The above snippet work absolutely fine. Is there anyway to send the build number as a json body.
api jenkins
asked Jan 2 at 11:14
AshwinAshwin
538
add a comment |
I'm trying to get the job status by providing the build number as a parameter.
curl -s -S -u "Ashwin":"XXX" "http://XX.XXX.XXX.XX:8080/job/apitest/buildNum/logText/progressiveText?start=0"
The above snippet work absolutely fine. Is there anyway to send the build number as a json body.
api jenkins
asked Jan 2 at 11:14
AshwinAshwin
538
add a comment |
I'm trying to get the job status by providing the build number as a parameter.
curl -s -S -u "Ashwin":"XXX" "http://XX.XXX.XXX.XX:8080/job/apitest/buildNum/logText/progressiveText?start=0"
The above snippet work absolutely fine. Is there anyway to send the build number as a json body.
api jenkins
asked Jan 2 at 11:14
AshwinAshwin
538
I'm trying to get the job status by providing the build number as a parameter.
curl -s -S -u "Ashwin":"XXX" "http://XX.XXX.XXX.XX:8080/job/apitest/buildNum/logText/progressiveText?start=0"
The above snippet work absolutely fine. Is there anyway to send the build number as a json body.
api jenkins
api jenkins
asked Jan 2 at 11:14
AshwinAshwin
538
asked Jan 2 at 11:14
AshwinAshwin
538
asked Jan 2 at 11:14
AshwinAshwin
538
asked Jan 2 at 11:14
AshwinAshwin
538
asked Jan 2 at 11:14
AshwinAshwin
538
538
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
In a word, no. The Jenkins API defines the query for the console log as a GET request, which (at least in the Jenkins API) does not contain a body. The primary parameters like job and build id are part of the URL path, and optional parameters are provided in the query string part of the URL.
This question strikes me as odd. Why can you not construct the query URL (which contains the build id as part of the URL path) in same way that you would construct the JSON structure that you propose sending in the body?
answered Jan 3 at 5:48
Dave BacherDave Bacher
13.1k24770
the intent was to use this request in POSTMAN application, where i can expose a set of query collection to my users. However even 'build' accepts json as url-encoded form and not raw. For now we are good with URL based parameters.
– Ashwin
Jan 4 at 7:38
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54005322%2fget-console-output-of-a-jenkins-job-by-sending-the-build-number-as-a-json-parame%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
In a word, no. The Jenkins API defines the query for the console log as a GET request, which (at least in the Jenkins API) does not contain a body. The primary parameters like job and build id are part of the URL path, and optional parameters are provided in the query string part of the URL.
This question strikes me as odd. Why can you not construct the query URL (which contains the build id as part of the URL path) in same way that you would construct the JSON structure that you propose sending in the body?
answered Jan 3 at 5:48
Dave BacherDave Bacher
13.1k24770
the intent was to use this request in POSTMAN application, where i can expose a set of query collection to my users. However even 'build' accepts json as url-encoded form and not raw. For now we are good with URL based parameters.
– Ashwin
Jan 4 at 7:38
add a comment |
In a word, no. The Jenkins API defines the query for the console log as a GET request, which (at least in the Jenkins API) does not contain a body. The primary parameters like job and build id are part of the URL path, and optional parameters are provided in the query string part of the URL.
This question strikes me as odd. Why can you not construct the query URL (which contains the build id as part of the URL path) in same way that you would construct the JSON structure that you propose sending in the body?
answered Jan 3 at 5:48
Dave BacherDave Bacher
13.1k24770
the intent was to use this request in POSTMAN application, where i can expose a set of query collection to my users. However even 'build' accepts json as url-encoded form and not raw. For now we are good with URL based parameters.
– Ashwin
Jan 4 at 7:38
add a comment |
In a word, no. The Jenkins API defines the query for the console log as a GET request, which (at least in the Jenkins API) does not contain a body. The primary parameters like job and build id are part of the URL path, and optional parameters are provided in the query string part of the URL.
This question strikes me as odd. Why can you not construct the query URL (which contains the build id as part of the URL path) in same way that you would construct the JSON structure that you propose sending in the body?
answered Jan 3 at 5:48
Dave BacherDave Bacher
13.1k24770
In a word, no. The Jenkins API defines the query for the console log as a GET request, which (at least in the Jenkins API) does not contain a body. The primary parameters like job and build id are part of the URL path, and optional parameters are provided in the query string part of the URL.
This question strikes me as odd. Why can you not construct the query URL (which contains the build id as part of the URL path) in same way that you would construct the JSON structure that you propose sending in the body?
answered Jan 3 at 5:48
Dave BacherDave Bacher
13.1k24770
answered Jan 3 at 5:48
Dave BacherDave Bacher
13.1k24770
answered Jan 3 at 5:48
Dave BacherDave Bacher
13.1k24770
answered Jan 3 at 5:48
Dave BacherDave Bacher
13.1k24770
13.1k24770
the intent was to use this request in POSTMAN application, where i can expose a set of query collection to my users. However even 'build' accepts json as url-encoded form and not raw. For now we are good with URL based parameters.
– Ashwin
Jan 4 at 7:38
add a comment |
the intent was to use this request in POSTMAN application, where i can expose a set of query collection to my users. However even 'build' accepts json as url-encoded form and not raw. For now we are good with URL based parameters.
– Ashwin
Jan 4 at 7:38
the intent was to use this request in POSTMAN application, where i can expose a set of query collection to my users. However even 'build' accepts json as url-encoded form and not raw. For now we are good with URL based parameters.
– Ashwin
Jan 4 at 7:38
the intent was to use this request in POSTMAN application, where i can expose a set of query collection to my users. However even 'build' accepts json as url-encoded form and not raw. For now we are good with URL based parameters.
– Ashwin
Jan 4 at 7:38
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54005322%2fget-console-output-of-a-jenkins-job-by-sending-the-build-number-as-a-json-parame%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
