on August 19, 2019
This is the first in a series of posts about simple things that I had a hard time figuring out in Azure DevOps services.
It can be very useful to enable Continuous Integration for multiple folders in your DevOps pipeline – say, for every branch created under releases/ or features/. But configuring this can be strangely confusing!
In this video, I show how to get a custom release branch folder set in your triggers for both build and release pipelines. Then I show a quick test of the automation at work in my demo pipeline.
Spoiler: the fix is to type directly into the filter box and hit enter. It looks like that box is only for filtering existing branches, but you can use it for edits! The fix starts in the video at 1:50.
REGISTER