TeamCity
 
2020.1
You are viewing the documentation for an earlier version of TeamCity.
  1. TeamCity Documentation
  2. Administrator's Guide
  3. Managing Projects and Build Configurations
  4. Configuring VCS Settings
  5. Configuring VCS Roots
  6. Perforce
  7. Perforce Streams as feature branches

Perforce Streams as feature branches

Edit page
Last modified: 23 July 2020

How to enable

On the VCS Root page, select checkbox "Enable feature branches support" after the parent stream name.

After that, all streams which have the specified main stream as a parent, will be included into the feature branches.

It is possible to specify some mapping to include only specific streams into the feature branches set, like +://stream-depot/*.

In this case, only streams under depot stream-depot will be included for changes collection/build triggering.

Task streams

Task streams are supported, but new task streams are not detected by TeamCity until there is a non-merge commit into this stream.

Remote run

Remote run from IDEA is possible only in a stream which was already detected by TeamCity. TeamCity remote run plugin tries to deduce the correct stream according to the depot paths of the files in the IDE working copy.

For instance, if a file path in the working copy starts with //depot/stream1/some/path, TeamCity will try finding //depot/stream1 stream and start remote run there.

But if you modified a file from another stream (imported into the working copy) and want to enforce build in a particular stream, you should specify a configuration parameter teamcity.build.branch when triggering the remote run.

Remote run of Perforce stream