Blacklisting branches for projects
We have separate projects/build configurations for development (master & other feature branches) and released versions (releases/*).
I don't know of an easy way to prevent someone from manually triggering a build on a development configuration with a release branch other than running a powershell script to fail the build if the branch name matches a certain pattern. Ideally released branches just wouldn't appear in the branches dropdown at all.
Is TC missing a feature or are we doing it wrong?
Oh, and we're using Git.
Please sign in to leave a comment.
Hi Flin,
When setting the VCS Root, you can set the default branch and a branch specification to use. You can simply exclude "releases/*" from the master/feature branches VCS Root and include only that one in the released configurations. You can even share the VCS Root and simply determine the branch specification via parameters defined in the build configuration.
More information here: https://confluence.jetbrains.com/display/TCD10/Working+with+Feature+Branches
Could you check whether this works for you?