Join Log in
Score:1
Sara June avatar Server

How to manage pipelines in multiple branches, in azure devops?

cn flag
Sara June

Let's say I have branch fetaure1, where there is pipeline file.

The trigger will be like this.

trigger:
   - feature1

For development purpose, I created a new branch from it say (feature1_deveoper1)

But, even though this new branch has this pipeline file, need to modify this again to get trigger working from it.

trigger:
   - feature1
   - feature1_developer1

So, after all my work, let's say I want to merge to the feature1 branch, again I need to remove this new feature entry and merge it to the branch.

Any better approach for this situation?

322
0 + 0
Score:0
avatar Server
cn flag
basscinner

Well, I know everyone has different workflows, but in a more traditional git usage pattern, like say gitflow, you wouldn't setup CI builds on short feature branches.

Each dev would of course make a feature branch off of a branch like say develop. They would work on the feature locally. When they're done, they make a PR, and it gets merged back into your bigger branch -- say develop or release or main or whatever.

That way the triggers section only needs to have the names of the main (long-lived) branches.

0 + 0
ธงชาติไทย
Elon Musk
I sit in a Tesla and translated this thread with Ai:

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.