Deployment triggers on new release branch
I've been doing some research for our team to migrate to a new branching strategy. Currently we are using the github flow with only master and feature branches. But since we have some trouble with hotfixes im thinking that we should migrate to the gitflow using release branches so we have a stable branch where we can do hotfixes when needed. We are using Azure Devops as our platform.
Anyway what im having trouble with so far is how should we trigger our continuous deployment pipelines when we create a new release branch?
Normally pipelines get triggered when a PR is merged and a CI build is run. However when you create a new release branch and want to deploy that to for example an Acceptance environment, how should we trigger those pipelines? Another problem is that we have multiple releaseable components in our repository. So when we create that release branch we would end up having to look up which components we changed, run manual build for them so our pipelines get triggered.
It seems to me this should be a common problem, yet i cant find much information on this, which suggests to me im missing something here. What am i missing?
Regards
How should we trigger our continuous deployment pipelines when we create a new release branch?
Since the resources you use are on github, you can try the following triggers configuration in Azure Devops Build Pipeline(CI) and Release Pipeline(CD).
Build Pipeline: You could add release branch to the branch filters. Then when you create a release branch or make changes in these two branches, the Pipeline will be triggered.
Release Pipeline: You could add the Build as artifacts resources. And you could also add the Release branch as the continuous deployment Branch filter.
In this case, the build triggered by the release branch will trigger the corresponding release.
These settings also ensure that the changes you make in the release branch can trigger CI and CD automatically.
Note: Github branches filters are case sensitive in Azure Devops.
- Should I merge master into a feature branch to bring it up to date? Would this be considered bad practice?
- Switch node_modules folder when I change git branch
- git p4 submit fails
- Assign the latest release in GitHub (not using git)
- How to sign out github account in vs code
- Visual Studio Team Explorer - GIT: Automatically ignoring new files
- Get modified files in Github actions
- Command to open file with git
- git - gpg onto mac osx: error: gpg failed to sign the data
- Git credential helper - update password
- How to remove cached credentials from Git?
- If I fork someone else's private Github repo into my account, is it going to appear in my account as a public repo?
- Using local git username and email on remote machine
- How do I delete all Git branches which have been merged?
- Switch to another Git tag
- Merging changes from master into my branch
- Refname 'master' is ambiguous
- git fetch origin --prune doesn't delete local branches?
- Git: warning: refname 'master' is ambiguous
- git: don't sort 'for-each-ref' output
- GitKraken won't open
- git shows files changed with 0 insertions(+), 0 deletions(-)
- How do I access my SSH public key?
- Can't push to GitHub because of large file which I already deleted
- Overwrite the master branch with a orphan branch in git
- Why did Git throw "Failed to load library 'libcurl-4.dll'" while cloning?
- In merge request gitlab ci shows error that previous job needs another job but is not in any previous stage but it is
- Git get history of branches that i was in
- How do you remove an invalid remote branch reference from Git?
- Git archive including the actual repository?