Automate multiple builds/ releases in Azure DevOpsVSTS build/release from multiple sources to Azure virtual directoriesAzure DevOps scheduled release with approvalsPublish snapshot artifacts to azure devops artifactsAzure DevOps Build Pipeline - A failed build still gets deployed to AzureAzure DevOps (VSTS) Pipeline (Release Definition) To Exclude Build Tag for Certain Stages (Environments)Is it possible to Import Azure DevOps Work ItemsChanging IIS Web Application Folder Path to Different Folder Before Releasing New Version of Code on Azure DevOps (VSTS)How to view Work Items associated with a Release in Azure DevOpsAzure DevOps - User triggering release as approverAzure DevOps Release Pipelines: Letting release flow through multiple environments with manual triggers

Exam design: give maximum score per question or not?

What is the maximum viable speed for a projectile within earth's atmosphere?

Manager manipulates my leaves, what's in it for him?

Unable to see packet drops on tunnels

What are sources for Magic Items that are not adventure-specific?

What is the rail connection between Paris Charles de Gaulle Airport and Gare de Lyon like?

All numbers in a 5x5 Minesweeper grid

Is there any actual security benefit to restricting foreign IPs?

Weapon class firing logic in JavaScript

Very lazy puppy

How often is duct tape used during crewed space missions?

Is it safe to unplug a blinking USB drive after 'safely' ejecting it?

Can I separate garlic into cloves for storage?

Is it possible that the shadow of The Moon is a single dot during solar eclipse?

How do you determine which representation of a function to use for Newton's method?

Lead Amalgam as a Material for a Sword

Madrid to London w/ Expired 90/180 days stay as US citizen

Twelve Minesweeper mines that make twelve 4s

Why would a fighter use the afterburner and air brakes at the same time?

How should I avoid someone patenting technology in my paper/poster?

What is the word for a person who destroys monuments?

Is Zack Morris's 'time stop' ability in "Saved By the Bell" a supernatural ability?

Cemented carbide swords - worth it?

Do household ovens ventilate heat to the outdoors?



Automate multiple builds/ releases in Azure DevOps


VSTS build/release from multiple sources to Azure virtual directoriesAzure DevOps scheduled release with approvalsPublish snapshot artifacts to azure devops artifactsAzure DevOps Build Pipeline - A failed build still gets deployed to AzureAzure DevOps (VSTS) Pipeline (Release Definition) To Exclude Build Tag for Certain Stages (Environments)Is it possible to Import Azure DevOps Work ItemsChanging IIS Web Application Folder Path to Different Folder Before Releasing New Version of Code on Azure DevOps (VSTS)How to view Work Items associated with a Release in Azure DevOpsAzure DevOps - User triggering release as approverAzure DevOps Release Pipelines: Letting release flow through multiple environments with manual triggers






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;








0















We have dozens of code repositories in Azure DevOps, and we're working on a major release strategy.



We have a stable development branch called develop, where code has been tested and peer-reviewed, with features approved by QA. All of our service repositories have a similar structure.



We want to "click a button" and branch from develop across all our repositories to a release candidate branch, that QA can regression test as a complete system... basically a "snapshot" of what we expect is ready for release. We would then build from this code base, release to our QA environment from the corresponding builds, and when certified, deploy to production, then smoke test and merge the release candidate branch into master, then master back into develop.



It doesn't seem like there's an easy way to manage multiple builds or releases in Azure DevOps though. Atlassian's Bamboo supported this concept of "meta builds" but I don't see a way to do this in Azure DevOps. I can't seem to even create a build that is not implicitly linked to a single repository.



How can I automate this and get this workflow working in Azure DevOps?










share|improve this question
























  • yeah, i dont think you can link build to multiple repos, you can use rest api to create branches in repos. that could work for you. but I'd have no idea how you would check all qaprod builds are success and make a decision on that. probably with rest api as well

    – 4c74356b41
    Mar 28 at 14:21











  • Not having tested this, I wonder if you can use a release pipeline with the repositories as the artifact(s) and then use the stages of the release to build/deploy/test. This might be the one place, push button style you're looking for, but "publishing" build artifacts isn't allowed from release pipelines, so you'll need to figure out how to do it without that mechanism.

    – Josh Gust
    Mar 28 at 15:57

















0















We have dozens of code repositories in Azure DevOps, and we're working on a major release strategy.



We have a stable development branch called develop, where code has been tested and peer-reviewed, with features approved by QA. All of our service repositories have a similar structure.



We want to "click a button" and branch from develop across all our repositories to a release candidate branch, that QA can regression test as a complete system... basically a "snapshot" of what we expect is ready for release. We would then build from this code base, release to our QA environment from the corresponding builds, and when certified, deploy to production, then smoke test and merge the release candidate branch into master, then master back into develop.



It doesn't seem like there's an easy way to manage multiple builds or releases in Azure DevOps though. Atlassian's Bamboo supported this concept of "meta builds" but I don't see a way to do this in Azure DevOps. I can't seem to even create a build that is not implicitly linked to a single repository.



How can I automate this and get this workflow working in Azure DevOps?










share|improve this question
























  • yeah, i dont think you can link build to multiple repos, you can use rest api to create branches in repos. that could work for you. but I'd have no idea how you would check all qaprod builds are success and make a decision on that. probably with rest api as well

    – 4c74356b41
    Mar 28 at 14:21











  • Not having tested this, I wonder if you can use a release pipeline with the repositories as the artifact(s) and then use the stages of the release to build/deploy/test. This might be the one place, push button style you're looking for, but "publishing" build artifacts isn't allowed from release pipelines, so you'll need to figure out how to do it without that mechanism.

    – Josh Gust
    Mar 28 at 15:57













0












0








0


1






We have dozens of code repositories in Azure DevOps, and we're working on a major release strategy.



We have a stable development branch called develop, where code has been tested and peer-reviewed, with features approved by QA. All of our service repositories have a similar structure.



We want to "click a button" and branch from develop across all our repositories to a release candidate branch, that QA can regression test as a complete system... basically a "snapshot" of what we expect is ready for release. We would then build from this code base, release to our QA environment from the corresponding builds, and when certified, deploy to production, then smoke test and merge the release candidate branch into master, then master back into develop.



It doesn't seem like there's an easy way to manage multiple builds or releases in Azure DevOps though. Atlassian's Bamboo supported this concept of "meta builds" but I don't see a way to do this in Azure DevOps. I can't seem to even create a build that is not implicitly linked to a single repository.



How can I automate this and get this workflow working in Azure DevOps?










share|improve this question














We have dozens of code repositories in Azure DevOps, and we're working on a major release strategy.



We have a stable development branch called develop, where code has been tested and peer-reviewed, with features approved by QA. All of our service repositories have a similar structure.



We want to "click a button" and branch from develop across all our repositories to a release candidate branch, that QA can regression test as a complete system... basically a "snapshot" of what we expect is ready for release. We would then build from this code base, release to our QA environment from the corresponding builds, and when certified, deploy to production, then smoke test and merge the release candidate branch into master, then master back into develop.



It doesn't seem like there's an easy way to manage multiple builds or releases in Azure DevOps though. Atlassian's Bamboo supported this concept of "meta builds" but I don't see a way to do this in Azure DevOps. I can't seem to even create a build that is not implicitly linked to a single repository.



How can I automate this and get this workflow working in Azure DevOps?







azure-devops azure-pipelines






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Mar 28 at 14:13









Jeremy HolovacsJeremy Holovacs

12.7k23 gold badges83 silver badges196 bronze badges




12.7k23 gold badges83 silver badges196 bronze badges















  • yeah, i dont think you can link build to multiple repos, you can use rest api to create branches in repos. that could work for you. but I'd have no idea how you would check all qaprod builds are success and make a decision on that. probably with rest api as well

    – 4c74356b41
    Mar 28 at 14:21











  • Not having tested this, I wonder if you can use a release pipeline with the repositories as the artifact(s) and then use the stages of the release to build/deploy/test. This might be the one place, push button style you're looking for, but "publishing" build artifacts isn't allowed from release pipelines, so you'll need to figure out how to do it without that mechanism.

    – Josh Gust
    Mar 28 at 15:57

















  • yeah, i dont think you can link build to multiple repos, you can use rest api to create branches in repos. that could work for you. but I'd have no idea how you would check all qaprod builds are success and make a decision on that. probably with rest api as well

    – 4c74356b41
    Mar 28 at 14:21











  • Not having tested this, I wonder if you can use a release pipeline with the repositories as the artifact(s) and then use the stages of the release to build/deploy/test. This might be the one place, push button style you're looking for, but "publishing" build artifacts isn't allowed from release pipelines, so you'll need to figure out how to do it without that mechanism.

    – Josh Gust
    Mar 28 at 15:57
















yeah, i dont think you can link build to multiple repos, you can use rest api to create branches in repos. that could work for you. but I'd have no idea how you would check all qaprod builds are success and make a decision on that. probably with rest api as well

– 4c74356b41
Mar 28 at 14:21





yeah, i dont think you can link build to multiple repos, you can use rest api to create branches in repos. that could work for you. but I'd have no idea how you would check all qaprod builds are success and make a decision on that. probably with rest api as well

– 4c74356b41
Mar 28 at 14:21













Not having tested this, I wonder if you can use a release pipeline with the repositories as the artifact(s) and then use the stages of the release to build/deploy/test. This might be the one place, push button style you're looking for, but "publishing" build artifacts isn't allowed from release pipelines, so you'll need to figure out how to do it without that mechanism.

– Josh Gust
Mar 28 at 15:57





Not having tested this, I wonder if you can use a release pipeline with the repositories as the artifact(s) and then use the stages of the release to build/deploy/test. This might be the one place, push button style you're looking for, but "publishing" build artifacts isn't allowed from release pipelines, so you'll need to figure out how to do it without that mechanism.

– Josh Gust
Mar 28 at 15:57












1 Answer
1






active

oldest

votes


















1
















You can use a Build Task from the Marketplace that queue a new build: the first two found are Trigger Build Task and Build Chain.
You defined an overarching build that queues the single ones and does any additional work.






share|improve this answer

























  • Unfortunately, this is the closest answer to my ideal that seems to exist. We'll probably hire a consultant to automate this through the RESTful APIs at some point though.

    – Jeremy Holovacs
    Apr 22 at 0:07










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/4.0/"u003ecc by-sa 4.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
);



);














draft saved

draft discarded
















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55399759%2fautomate-multiple-builds-releases-in-azure-devops%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









1
















You can use a Build Task from the Marketplace that queue a new build: the first two found are Trigger Build Task and Build Chain.
You defined an overarching build that queues the single ones and does any additional work.






share|improve this answer

























  • Unfortunately, this is the closest answer to my ideal that seems to exist. We'll probably hire a consultant to automate this through the RESTful APIs at some point though.

    – Jeremy Holovacs
    Apr 22 at 0:07















1
















You can use a Build Task from the Marketplace that queue a new build: the first two found are Trigger Build Task and Build Chain.
You defined an overarching build that queues the single ones and does any additional work.






share|improve this answer

























  • Unfortunately, this is the closest answer to my ideal that seems to exist. We'll probably hire a consultant to automate this through the RESTful APIs at some point though.

    – Jeremy Holovacs
    Apr 22 at 0:07













1














1










1









You can use a Build Task from the Marketplace that queue a new build: the first two found are Trigger Build Task and Build Chain.
You defined an overarching build that queues the single ones and does any additional work.






share|improve this answer













You can use a Build Task from the Marketplace that queue a new build: the first two found are Trigger Build Task and Build Chain.
You defined an overarching build that queues the single ones and does any additional work.







share|improve this answer












share|improve this answer



share|improve this answer










answered Mar 28 at 15:38









Giulio VianGiulio Vian

7,3082 gold badges25 silver badges36 bronze badges




7,3082 gold badges25 silver badges36 bronze badges















  • Unfortunately, this is the closest answer to my ideal that seems to exist. We'll probably hire a consultant to automate this through the RESTful APIs at some point though.

    – Jeremy Holovacs
    Apr 22 at 0:07

















  • Unfortunately, this is the closest answer to my ideal that seems to exist. We'll probably hire a consultant to automate this through the RESTful APIs at some point though.

    – Jeremy Holovacs
    Apr 22 at 0:07
















Unfortunately, this is the closest answer to my ideal that seems to exist. We'll probably hire a consultant to automate this through the RESTful APIs at some point though.

– Jeremy Holovacs
Apr 22 at 0:07





Unfortunately, this is the closest answer to my ideal that seems to exist. We'll probably hire a consultant to automate this through the RESTful APIs at some point though.

– Jeremy Holovacs
Apr 22 at 0:07








Got a question that you can’t ask on public Stack Overflow? Learn more about sharing private information with Stack Overflow for Teams.







Got a question that you can’t ask on public Stack Overflow? Learn more about sharing private information with Stack Overflow for Teams.




















draft saved

draft discarded















































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.




draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55399759%2fautomate-multiple-builds-releases-in-azure-devops%23new-answer', 'question_page');

);

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







Popular posts from this blog

Kamusi Yaliyomo Aina za kamusi | Muundo wa kamusi | Faida za kamusi | Dhima ya picha katika kamusi | Marejeo | Tazama pia | Viungo vya nje | UrambazajiKuhusu kamusiGo-SwahiliWiki-KamusiKamusi ya Kiswahili na Kiingerezakuihariri na kuongeza habari

SQL error code 1064 with creating Laravel foreign keysForeign key constraints: When to use ON UPDATE and ON DELETEDropping column with foreign key Laravel error: General error: 1025 Error on renameLaravel SQL Can't create tableLaravel Migration foreign key errorLaravel php artisan migrate:refresh giving a syntax errorSQLSTATE[42S01]: Base table or view already exists or Base table or view already exists: 1050 Tableerror in migrating laravel file to xampp serverSyntax error or access violation: 1064:syntax to use near 'unsigned not null, modelName varchar(191) not null, title varchar(191) not nLaravel cannot create new table field in mysqlLaravel 5.7:Last migration creates table but is not registered in the migration table

은진 송씨 목차 역사 본관 분파 인물 조선 왕실과의 인척 관계 집성촌 항렬자 인구 같이 보기 각주 둘러보기 메뉴은진 송씨세종실록 149권, 지리지 충청도 공주목 은진현