How to run pipeline after release pipeline in VSTS?
I have a task which I would like to run after the completion of any of my release pipelines. The release pipelines need to complete their run and finish completely. Then this final pipeline should run and be passed the artefact from the build and release pipeline.
Is there a way to run a task or pipeline after a release pipeline has completed?
I need to run this task after the release pipeline has completed because the task I've written needs to request information from the DevOps REST API which will not return anything until the release pipeline has finished.
azure-devops azure-pipelines asked Nov 12 at 6:43
Matt W
3,608115299
|
show 3 more comments
I have a task which I would like to run after the completion of any of my release pipelines. The release pipelines need to complete their run and finish completely. Then this final pipeline should run and be passed the artefact from the build and release pipeline.
Is there a way to run a task or pipeline after a release pipeline has completed?
I need to run this task after the release pipeline has completed because the task I've written needs to request information from the DevOps REST API which will not return anything until the release pipeline has finished.
azure-devops azure-pipelines asked Nov 12 at 6:43
Matt W
3,608115299
1
Have you tried setting up another job, does the rest api return values after job is completed? You could also implement azure function and add one step to invoke that function when release is completed. Then wait(?) in azure function and do your magic.
– Panu Oksala
Nov 12 at 7:01
I tried setting up another pipeline to be run after the release pipeline, but that is not possible, AFAIK. The API only returns information generated during the pipeline run after the pipeline has fully completed. I will look into using azure functions, though it would be nicer to keep all the work in one place.
– Matt W
Nov 12 at 8:13
1
Oh, ok. You are right that one place would be nice, but I have found that often it's not possible if you are doing anything bit more complex. In my blog is a short tutorial how to create custom integration with Azure DevOps (oksala.net). Check it out and hopefully it helps ya.
– Panu Oksala
Nov 12 at 10:41
1
at the end of the first pipeline, you can add a task that kicks off a new release pipeline, until the new pipeline will start the first will be finished.
– Shayki Abramczyk
Nov 12 at 10:59
1
You can also do it with Service Hook, do you know what is it?
– Shayki Abramczyk
Nov 12 at 11:22
|
show 3 more comments
I have a task which I would like to run after the completion of any of my release pipelines. The release pipelines need to complete their run and finish completely. Then this final pipeline should run and be passed the artefact from the build and release pipeline.
Is there a way to run a task or pipeline after a release pipeline has completed?
I need to run this task after the release pipeline has completed because the task I've written needs to request information from the DevOps REST API which will not return anything until the release pipeline has finished.
azure-devops azure-pipelines asked Nov 12 at 6:43
Matt W
3,608115299
I have a task which I would like to run after the completion of any of my release pipelines. The release pipelines need to complete their run and finish completely. Then this final pipeline should run and be passed the artefact from the build and release pipeline.
Is there a way to run a task or pipeline after a release pipeline has completed?
I need to run this task after the release pipeline has completed because the task I've written needs to request information from the DevOps REST API which will not return anything until the release pipeline has finished.
azure-devops azure-pipelines azure-devops azure-pipelines asked Nov 12 at 6:43
Matt W
3,608115299
asked Nov 12 at 6:43
Matt W
3,608115299
asked Nov 12 at 6:43
Matt W
3,608115299
asked Nov 12 at 6:43
Matt W
3,608115299
asked Nov 12 at 6:43
Matt W
3,608115299
3,608115299
1
Have you tried setting up another job, does the rest api return values after job is completed? You could also implement azure function and add one step to invoke that function when release is completed. Then wait(?) in azure function and do your magic.
– Panu Oksala
Nov 12 at 7:01
I tried setting up another pipeline to be run after the release pipeline, but that is not possible, AFAIK. The API only returns information generated during the pipeline run after the pipeline has fully completed. I will look into using azure functions, though it would be nicer to keep all the work in one place.
– Matt W
Nov 12 at 8:13
1
Oh, ok. You are right that one place would be nice, but I have found that often it's not possible if you are doing anything bit more complex. In my blog is a short tutorial how to create custom integration with Azure DevOps (oksala.net). Check it out and hopefully it helps ya.
– Panu Oksala
Nov 12 at 10:41
1
at the end of the first pipeline, you can add a task that kicks off a new release pipeline, until the new pipeline will start the first will be finished.
– Shayki Abramczyk
Nov 12 at 10:59
1
You can also do it with Service Hook, do you know what is it?
– Shayki Abramczyk
Nov 12 at 11:22
|
show 3 more comments
1
Have you tried setting up another job, does the rest api return values after job is completed? You could also implement azure function and add one step to invoke that function when release is completed. Then wait(?) in azure function and do your magic.
– Panu Oksala
Nov 12 at 7:01
I tried setting up another pipeline to be run after the release pipeline, but that is not possible, AFAIK. The API only returns information generated during the pipeline run after the pipeline has fully completed. I will look into using azure functions, though it would be nicer to keep all the work in one place.
– Matt W
Nov 12 at 8:13
1
Oh, ok. You are right that one place would be nice, but I have found that often it's not possible if you are doing anything bit more complex. In my blog is a short tutorial how to create custom integration with Azure DevOps (oksala.net). Check it out and hopefully it helps ya.
– Panu Oksala
Nov 12 at 10:41
1
at the end of the first pipeline, you can add a task that kicks off a new release pipeline, until the new pipeline will start the first will be finished.
– Shayki Abramczyk
Nov 12 at 10:59
1
You can also do it with Service Hook, do you know what is it?
– Shayki Abramczyk
Nov 12 at 11:22
1
1
Have you tried setting up another job, does the rest api return values after job is completed? You could also implement azure function and add one step to invoke that function when release is completed. Then wait(?) in azure function and do your magic.
– Panu Oksala
Nov 12 at 7:01
Have you tried setting up another job, does the rest api return values after job is completed? You could also implement azure function and add one step to invoke that function when release is completed. Then wait(?) in azure function and do your magic.
– Panu Oksala
Nov 12 at 7:01
I tried setting up another pipeline to be run after the release pipeline, but that is not possible, AFAIK. The API only returns information generated during the pipeline run after the pipeline has fully completed. I will look into using azure functions, though it would be nicer to keep all the work in one place.
– Matt W
Nov 12 at 8:13
I tried setting up another pipeline to be run after the release pipeline, but that is not possible, AFAIK. The API only returns information generated during the pipeline run after the pipeline has fully completed. I will look into using azure functions, though it would be nicer to keep all the work in one place.
– Matt W
Nov 12 at 8:13
1
1
Oh, ok. You are right that one place would be nice, but I have found that often it's not possible if you are doing anything bit more complex. In my blog is a short tutorial how to create custom integration with Azure DevOps (oksala.net). Check it out and hopefully it helps ya.
– Panu Oksala
Nov 12 at 10:41
Oh, ok. You are right that one place would be nice, but I have found that often it's not possible if you are doing anything bit more complex. In my blog is a short tutorial how to create custom integration with Azure DevOps (oksala.net). Check it out and hopefully it helps ya.
– Panu Oksala
Nov 12 at 10:41
1
1
at the end of the first pipeline, you can add a task that kicks off a new release pipeline, until the new pipeline will start the first will be finished.
– Shayki Abramczyk
Nov 12 at 10:59
at the end of the first pipeline, you can add a task that kicks off a new release pipeline, until the new pipeline will start the first will be finished.
– Shayki Abramczyk
Nov 12 at 10:59
1
1
You can also do it with Service Hook, do you know what is it?
– Shayki Abramczyk
Nov 12 at 11:22
You can also do it with Service Hook, do you know what is it?
– Shayki Abramczyk
Nov 12 at 11:22
|
show 3 more comments
1 Answer
1
active
oldest
votes
There is an extension in the Marketplace called "Trigger Build Task" (https://marketplace.visualstudio.com/items?itemName=benjhuser.tfs-extensions-build-tasks) that enables the chaining builds.
It allows your Release pipeline to complete and a separate Build pipeline is started on a different thread/process, so you should be able to query the information you need from that triggered Build.
answered Nov 12 at 14:27
SitWalkStand
1,0211011
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%2f53257066%2fhow-to-run-pipeline-after-release-pipeline-in-vsts%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
There is an extension in the Marketplace called "Trigger Build Task" (https://marketplace.visualstudio.com/items?itemName=benjhuser.tfs-extensions-build-tasks) that enables the chaining builds.
It allows your Release pipeline to complete and a separate Build pipeline is started on a different thread/process, so you should be able to query the information you need from that triggered Build.
answered Nov 12 at 14:27
SitWalkStand
1,0211011
add a comment |
There is an extension in the Marketplace called "Trigger Build Task" (https://marketplace.visualstudio.com/items?itemName=benjhuser.tfs-extensions-build-tasks) that enables the chaining builds.
It allows your Release pipeline to complete and a separate Build pipeline is started on a different thread/process, so you should be able to query the information you need from that triggered Build.
answered Nov 12 at 14:27
SitWalkStand
1,0211011
add a comment |
There is an extension in the Marketplace called "Trigger Build Task" (https://marketplace.visualstudio.com/items?itemName=benjhuser.tfs-extensions-build-tasks) that enables the chaining builds.
It allows your Release pipeline to complete and a separate Build pipeline is started on a different thread/process, so you should be able to query the information you need from that triggered Build.
answered Nov 12 at 14:27
SitWalkStand
1,0211011
There is an extension in the Marketplace called "Trigger Build Task" (https://marketplace.visualstudio.com/items?itemName=benjhuser.tfs-extensions-build-tasks) that enables the chaining builds.
It allows your Release pipeline to complete and a separate Build pipeline is started on a different thread/process, so you should be able to query the information you need from that triggered Build.
answered Nov 12 at 14:27
SitWalkStand
1,0211011
answered Nov 12 at 14:27
SitWalkStand
1,0211011
answered Nov 12 at 14:27
SitWalkStand
1,0211011
answered Nov 12 at 14:27
SitWalkStand
1,0211011
1,0211011
add a comment |
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f53257066%2fhow-to-run-pipeline-after-release-pipeline-in-vsts%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
1
Have you tried setting up another job, does the rest api return values after job is completed? You could also implement azure function and add one step to invoke that function when release is completed. Then wait(?) in azure function and do your magic.
– Panu Oksala
Nov 12 at 7:01
I tried setting up another pipeline to be run after the release pipeline, but that is not possible, AFAIK. The API only returns information generated during the pipeline run after the pipeline has fully completed. I will look into using azure functions, though it would be nicer to keep all the work in one place.
– Matt W
Nov 12 at 8:13
1
Oh, ok. You are right that one place would be nice, but I have found that often it's not possible if you are doing anything bit more complex. In my blog is a short tutorial how to create custom integration with Azure DevOps (oksala.net). Check it out and hopefully it helps ya.
– Panu Oksala
Nov 12 at 10:41
1
at the end of the first pipeline, you can add a task that kicks off a new release pipeline, until the new pipeline will start the first will be finished.
– Shayki Abramczyk
Nov 12 at 10:59
1
You can also do it with Service Hook, do you know what is it?
– Shayki Abramczyk
Nov 12 at 11:22