The line can also contain optional parentheses which, when present, denote the part of the pattern to be used as the logical name instead of just *-matched symbols. The part of the branch name matched by the asterisk ( *) wildcard becomes the short branch name to be displayed in the TeamCity user-level interface (also known as the logical branch name). The branch_name parameter is VCS-specific, i.e. The branch with refs/heads/teamcity will not be matched. For example, +:refs/heads/teamcity* matches all branches starting with refs/heads/teamcity and at least one additional character. Here, the pipe symbol | represents the OR command, as in regular expressions: use + for including, OR - for excluding.Įach rule can have one optional * placeholder which matches one or more characters. The syntax of the branch specification field is newline-delimited list of +|-:branch_name rules. Branch names will also appear in the custom build dialog, so you'll be able to manually trigger a custom build on a branch too. From the build configuration home page you'll also be able to filter the history, change log, pending changes and issue log by the branch name. If your build configuration has a VCS trigger and a change is found in some branch, TeamCity will trigger a build in this branch. Once you've configured the branch specification, TeamCity will start to monitor these branches for changes. TeamCity monitors the branches matched by the branch specification in addition to the default branch. The field accepts a list of branch names or patterns. With Perforce, check the corresponding box to enable feature branches support, which will display the branch specification field. This is done in the General Settings section of a Git or Mercurial VCS root via the Branch Specification field. To start working with DVCS branches, you need to configure which branches need to be watched for changes. Git and Mercurial feature branches are supported as well as Perforce branch streams support. TeamCity support for feature branches is continuously extending and, among other features, includes Branch Remote Run Trigger starting a new personal build each time TeamCity detects changes in a particular branches of the VCS roots of the build configuration and Automatic Merge to merge a branch into another after a successful build. This approach brings a number of advantages to software development teams however, in continuous integration servers that do not have dedicated support for it, it also causes a number of problems, like constant build configurations duplication, poor visibility, and, in the end, loss of control over the process. Feature branches in distributed version control systems (DVCS) allow you to work on a feature independently of the main development and commit all the changes for the feature onto the branch, merging the changes into the main branch when your feature is complete.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |