Answered

Process for committing changes to a branch?

(0) Share

Report

Posted on by Cooper01

664

Let's say I have a feature branch, created from main. My updates for this feature include changes to a canvas app in a solution. Is there a way to automate the process of extracting the solution to source control when it's not in the main branch? I know how to create a pipeline to do this but when I create the pipeline I have to first select the branch. So is there any way to have a pipeline that points to a dynamic branch so I can run it on whatever branch I need to?

Ultimately I'd like to

Create the branch
Complete dev work
Add the work to the new branch
Create a pull request and merge to main

Categories:

Application Lifecycle Management (ALM)

All responses (2)

Answers (1)

Cooper01 664 on at

Like (0)

Report

Re: Process for committing changes to a branch?

OMG. Have been running my pipelines from the editor and did not realize there was a Branch/tag ddl when you run it from the export list. I was mainly trying to avoid having to make developers spin up a new pipeline for each branch they create so I believe this solves the issue. Thanks @ScottDurow !!
Verified answer

ScottDurow 1,039 on at

Like (0)

Report
Re: Process for committing changes to a branch?

I think the challenge you are referring to is where you need your pipeline to point to an envrionment to unpack from depending on the branch you are running it on.
When you run a pipeline you can select the branch - I then use a convention where I use a variable set that is named the same as the branch to provide the SPN etc. to use to connect to the corresponding environment that goes with that branch.
I then load that variable set using something like:
variables: - group: branch-environment-${{ variables['Build.SourceBranchName'] }}

This way you can have a single pipeline that can be run on different branches and will pick up the environment details registered for that branch.
Hope this helps