Remotely running builds on Perforce streams. The remote run/debug functionality is common for all types of VCS, but there are extra conveniences specific to Perforce: If you write code in an IntelliJ-based IDE, you can pretest and prebuild local changes before committing them to a main Perforce repository: see common instructions on remote run, remote debug, and pre-test delayed commits. Running Personal Builds from IntelliJ IDE To save the server resources, you can clean inactive workspaces created by TeamCity directly from the TeamCity UI. To properly process task streams, TeamCity needs to create dedicated workspaces on the Perforce server. If you have modified a file from another stream (imported into the working copy) and want to enforce a build in a particular stream, you need to specify a configuration parameter when triggering the remote run. For instance, if a file path in the working copy starts with //depot/stream1/some/path, TeamCity will try finding the //depot/stream1 stream and starting the remote run there. The TeamCity Remote Run plugin tries to deduce the correct stream according to the depot paths of the files in the IDE's working copy. You can launch a remote build run from IntelliJ-platform IDEs, but only if a stream has been already detected by TeamCity. Running Builds on Streams from IntelliJ IDE TeamCity can process task streams as well, but it only detects new task streams if there is a non-merge commit made to them. Here, the pipe symbol | represents the OR command, as in regular expressions: use + for including, OR - for excluding. For example, use +://stream-depot/* to monitor only streams located in the stream-depot depot, where * (for example, master) is a logical branch name. Each filter rule should start with a new line. To include only specific streams to this set, edit the branch specification to filter these streams. After it is enabled, all streams which have the specified main stream as a parent will be included into the set of feature branches processed by TeamCity. If a Perforce root is configured to use the Stream mode, you can enable the feature branches support in the root settings. TeamCity can monitor commits in Perforce streams and work with them as with regular feature branches. In the Project Settings, go to VCS Roots.Ĭhoose Perforce Helix Core as a VCS type.Ĭonfigure the root's settings as described in this article.Īfter the project and Perforce root are configured, you can proceed with adding build configurations and running builds. Alternatively, you can add it under any other existing project. Note that this will add the project right under the Root project. Go to Administration | Projects and click Create project. To be able to run builds on project sources stored in Perforce Helix Core and to use all the features described in this article, you need to perform two procedures: Running Builds on Perforce Helix Core Sources The property value must include the p4 filename. Alternatively, a full path to p4 could be set via the internal property 4Path. The path to the Perforce client must be added to the PATH environment variable. TeamCity supports Perforce Helix Core servers/clients starting from Helix Core 2017.1Ī Perforce Helix Core client must be installed on the TeamCity server machine. Report build statuses to code reviews in Perforce Helix Swarm. Pre-test and pre-build files in shelved changelists. Use Perforce streams as feature branches and build their sources independently of each other. This article describes how to integrate TeamCity with Perforce Helix Core to:īuild sources of projects stored in a Helix Core repository.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |