Azure-devops-docs: Is this process automated, or manual?

[ronnyek]

I'm just genuinely interested in how the release branches are created... a person manually going and creating a branch at the beginning of the sprint? Have you guys set up some form of automation to create the sprint release branch?

I appreciate the input!

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: d1235ec4-e7e9-b0c2-8f1f-ee9682175a05
• Version Independent ID: a473750a-fbb6-4eed-e0e6-34e8a5009507
• Content: Release Flow - Azure DevOps
• Content Source: https://mseng.visualstudio.com/DefaultCollection/TechnicalContent/_git/devops-learn-pr?path=%2fdocs%2fdevops-at-microsoft%2frelease-flow.md&version=GBlive&_a=contents
• Product: devops
• Git Login: samgu
• Microsoft Alias: ethomson

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[true-zanuda]

I'm still interested in a response.

[alainvezina]

Me too super interested!!

[tgdane]

We are using this branching strategy and have automated the release branching using a script that essentially determines the next version number (by getting a list of branches matching releases/*, last version +1) then creates a new branch with the new version number. Push the new branch and have your CI/CD triggers on master and releases/*. The creation of a new release is essentially a business decision, so automate the process but trigger it on demand. But it could be scheduled if that works better. Hope that helps.

[FixRM]

Hi @tgdane, can you please share more details about CI/СD triggers you use?

[cxwtool]

This issue hasn't been updated in more than 180 days, so we've closed it. If you feel the issue is still relevant and needs fixed, please reopen it and we'll take another look. We appreciate your feedback and apologize for any inconvenience.