What's New in TeamCity 8.0 - TeamCity 8.x Documentation. Projects Hierarchy TeamCity 8.0 allows creating subprojects inside other projects. Now all projects form a tree (each project can have one parent project only) with the <Root project> at the top of the hierarchy. The <Root project> is created by default and cannot be removed. Project hierarchy affects the server behavior in many places: VCS roots created in a project are available in this project and in all subprojects down the hierarchy.
As such, the concept of shared VCS root has been eliminated, and all shared roots are moved to the <Root project> during upgrade. Similarly to VCS roots, build configuration templates created in a project are available in this project and in all subprojects. Different pages in the user interface now include results from subprojects: The project Change Log page now shows changes from the current project and all subprojects. Human Friendly Identifiers Related topic in our documentation: Identifier Project Directory Structure Mixed Mode Authentication. REST API Plugin - TeamCity.
Skip to end of metadataGo to start of metadata On this page: General Info Plugin Description Exposes the TeamCity API via REST. Usage Details of the API usage are described at the version-specific pages: REST API Versions As REST API evolves from one TeamCity version to another, there can be incompatible changes in the protocol. API Changes Breaking changes in the API are described in Upgrade Notes sections of the corresponding TeamCity version documentation. Logging You can get details on errors and REST request processing in logs\teamcity-rest.log server log. Development links Sources If you need to extend the plugin with your functionality, you can base your plugin on the current REST API plugin code, but make sure that your plugin does not interfere with the bundled REST plugin.
TeamCity Versions Compatibility TeamCity 5.0 and above. Feedback Feel free to ask questions and provide feedback in our plugins forum. What's New in TeamCity 7.1 - TeamCity 7.x Documentation. Feature branches for Git & Mercurial Distributed version control systems like Git & Mercurial provide a convenient way to develop in feature branches. Previous versions of TeamCity already supported development in feature branches to some extent. Prior to TeamCity 7.1 you could: Both ways have disadvantages. Creating a new build configuration for each branch is tedious and requires permissions, and it does not provide the same feeling as creating a branch in Git.
On the other hand Branch Remote Run Trigger can trigger personal builds only (by default, such builds are only visible to the build owner), so this approach does not work well if more than one developer works in a feature branch. These ways look like workarounds, so we felt a new approach was required to make TeamCity fully compatible with this development model. Our main idea was to make development and building in branches as simple as possible. Branch specification & default branch VCS trigger Branch label on a build Dependencies.
TeamCity Plugins - TeamCity. TeamCity. Continuous Integration for Everybody — TeamCity.