Included all latest build artifacts for branch in release

%3CLINGO-SUB%20id%3D%22lingo-sub-2499382%22%20slang%3D%22en-US%22%3EIncluded%20all%20latest%20build%20artifacts%20for%20branch%20in%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2499382%22%20slang%3D%22en-US%22%3E%3CP%3EHello!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20pretty%20new%20to%20the%20DevOps%20world%20and%20I'm%20curious%20to%20figure%20out%20how%20I%20can%20align%20all%20the%20outputs%20of%20all%20my%20pipelines%20to%20come%20from%20the%20source%20branch%20when%20a%20release%20is%20created.%20We%20currently%20do%20all%20Pull%20Requests%20into%20a%20develop%20branch%20during%20our%20three%20week%20sprint%20cycles%20and%20then%20once%20a%20Sprint%20is%20finished%20we%20cut%20a%20release%20branch%20that%20is%20named%20%22releases%2FX.Y.Z%22%20where%20%22X.Y.Z%22%20is%20the%20final%20version%20of%20the%20main%20application%20we%20sell%20to%20our%20customers.%20This%20means%20that%20we'll%20have%20a%20new%20release%20branch%20name%20at%20the%20end%20of%20every%20sprint.%26nbsp%3B%20Along%20with%20our%20main%20application%20we%20also%20have%209%20other%20build%20artifacts%20that%20we%20include%2C%20each%20coming%20from%20their%20own%20build%20pipelines.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20we%20are%20trying%20to%20accomplish%2C%20or%20find%20a%20better%20approach%20to%20our%20implementation%2C%20is%20that%20when%20a%20new%20build%20artifact%20is%20available%20for%20any%20of%20the%2010%20pipelines%2C%20we%20want%20a%20new%20release%20to%20show%20up%20on%20the%20board%20that%20only%20contains%20the%20latest%20artifacts%20from%20ALL%2010%20of%20the%20pipeline%20artifacts%20for%20the%20release%20branch%20that%20was%20just%20updated.%20Meaning%2C%20if%20I%20click%20on%20the%20release%20and%20view%20the%20Release%20Artifacts%2C%20each%20one%20is%20coming%20from%20the%20same%20branch.%20And%20if%20I%20verify%20the%20versions%20of%20each%2C%20they%20are%20all%20the%20latest%20build%20output.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EExample%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENew%20files%20are%20checked%20into%20the%20releases%2F1.2.3%20branch%20which%20triggers%20%22Build%20A%22%20to%20wake%20up%20and%20perform%20it's%20work.%20Once%20it%20is%20completed%2C%20the%20Release%20board%20will%20be%20triggered%20to%20generate%20a%20new%20release%20with%20the%20changes%20made%20to%20releases%2F1.2.3.%26nbsp%3BHowever%2C%20instead%20of%20the%20release%20pipeline%20grabbing%20the%20latest%20version%20of%20the%20latest%20output%20for%20the%209%20remaining%20Build%20Artifacts%20that%20are%20included%20in%20the%20release%2C%20we%20need%20it%20to%20grab%20the%20latest%20Build%20outputs%20from%20the%20releases%2F1.2.3%20branch%20specifically.%20Thus%20ensuring%20that%20everything%20that%20is%20being%20deployed%20is%20coming%20from%20the%20same%20branch.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20are%20currently%20using%20the%20same%20board%20to%20deploy%20releases%20from%20the%20develop%20branch%20and%20any%20branch%20in%20the%20releases%2F*%20folder.%20This%20seems%20to%20be%20causing%20most%20of%20the%20issues%20with%20our%20board%20deploying%20artifacts%20from%20different%20branches.%20We%20need%20the%20system%20ensure%20that%20all%20releases%20contain%20artifacts%20from%20the%20same%20branch%20that%20caused%20the%20release%20to%20be%20generated.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20insight%20to%20get%20this%20working%20or%20an%20alternative%20solution%20to%20get%20around%20this%20would%20be%20greatly%20appreciated.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EEDIT%3A%20We're%20using%20the%20Classic%20editor%20if%20that%20makes%20a%20difference.%20Not%20opposed%20to%20going%20YAML%20if%20it%20will%20give%20us%20what%20we%20need.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%2C%3C%2FP%3E%3CP%3EBrent%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Visitor

Hello!

 

I'm pretty new to the DevOps world and I'm curious to figure out how I can align all the outputs of all my pipelines to come from the source branch when a release is created. We currently do all Pull Requests into a develop branch during our three week sprint cycles and then once a Sprint is finished we cut a release branch that is named "releases/X.Y.Z" where "X.Y.Z" is the final version of the main application we sell to our customers. This means that we'll have a new release branch name at the end of every sprint.  Along with our main application we also have 9 other build artifacts that we include, each coming from their own build pipelines.

 

What we are trying to accomplish, or find a better approach to our implementation, is that when a new build artifact is available for any of the 10 pipelines, we want a new release to show up on the board that only contains the latest artifacts from ALL 10 of the pipeline artifacts for the release branch that was just updated. Meaning, if I click on the release and view the Release Artifacts, each one is coming from the same branch. And if I verify the versions of each, they are all the latest build output.

 

Example:

 

New files are checked into the releases/1.2.3 branch which triggers "Build A" to wake up and perform it's work. Once it is completed, the Release board will be triggered to generate a new release with the changes made to releases/1.2.3. However, instead of the release pipeline grabbing the latest version of the latest output for the 9 remaining Build Artifacts that are included in the release, we need it to grab the latest Build outputs from the releases/1.2.3 branch specifically. Thus ensuring that everything that is being deployed is coming from the same branch.

 

We are currently using the same board to deploy releases from the develop branch and any branch in the releases/* folder. This seems to be causing most of the issues with our board deploying artifacts from different branches. We need the system ensure that all releases contain artifacts from the same branch that caused the release to be generated.

 

Any insight to get this working or an alternative solution to get around this would be greatly appreciated.

 

EDIT: We're using the Classic editor if that makes a difference. Not opposed to going YAML if it will give us what we need.

 

Thanks,

Brent

 

1 Reply
I suppose you can create a Gate or receive a hook to Azure function with target branch and trigger all the releases from that branch