Enable CI against all Branches
Branching strategies varies from Client to Client/ Project to Project, but the common practices teams are looking for enabling CI against all your branches.
In this post, I will show how we can configure CI against all the branchs.
When you create a build, it enables CI against the ‘master’ branch. But how you can enable the CI against all your branches. It’s a simple but powerful trick. Azure DevOps use branch filter will help you to achieve this. You can use this option by mention all your branch types/ category e.g. features/ bugs/ hotfixes.
Watch demo for more details
Related Posts
- Getting the Most from GitHub Copilot and AI Models - Boost Productivity While Managing Costs
- Branch Protection as Code Enforce GitHub Security at Scale
- DevOps Attitude
- Manage Azure DevOps Pipelines Variables
- VSTS Build and Release Agents
About Ajeet Chouksey
Ajeet Chouksey
Subscribe via Email
Recent Posts
- Getting the Most from GitHub Copilot and AI Models - Boost Productivity While Managing Costs
- The Evolving Role of the Product Owner in the Age of AI
- Supercharging Code Reviews with AI for Strategic Impact
- Branch Protection as Code Enforce GitHub Security at Scale
- Governance Layer Best Practices in GitHub
- Deploy and Configure SonarQube
- Azure Bastion
- DevOps Attitude