We are working on the project import and in this EAP an initial version of this feature is presented. So far the import is possible only from a backup file produced using the current version of TeamCity. It is by design that we do not support importing projects from old-version backup files. To import projects, a backup file should be placed into the
<TeamCity Data Directory>/import directory.
The following data is not imported:
- Build logs
- Personal changes files (we import personal builds and their data, but don't import changed files)
- Code Duplicate inspections
- Audit records
- User roles definitions (from the
- Old tables 'vcs_changes' and 'personal_vcs_changes'
Known Security issues
- Imported users can get higher-level permissions (e.g. system administrator role) on the target server (if the source/target server have different
roles-config.xmlor groups with the same keys have different set of roles granted)
- User groups are merged by their string Id. So, if the servers have semantically different groups with the same name, imported users might end up in the wrong groups.
Starting from this EAP, to easily access builds you want to monitor, you can mark them as favorite. Any manually triggered build will be marked as favorite automatically. The marked builds will be listed on the "My Favorite Builds" page. In addition, notification rules can be configured for such builds.
Managing custom charts from the TeamCity Web UI
Before this build, you could manage your custom charts by manually modifying the
TeamCity Data Directory
>/pluginData/plugin-settings.xml file. Now you can create a new chart:
- on the Statistics tab for a project or build configuration using the Add new chart button. Note that only one build configuration can be currently added as the data source.
- on the Parameters tab of the build results page, where the list of Reported statistic values provides checkboxes to select the statistics type for a new project- or build-configuration-level chart.
Modifying custom charts now can also be easily done from the TeamCity Web UI.
More details on this feature are available in our documentation.
Create build configuration from Meta-Runner
Currently to change a Meta-Runner you have to edit xml file. This is a error-prone process. Not to mention that if a Meta-Runner is already used, changing it without the ability to test it first may fail a lot of builds. To make this process easier, we introduced an ability to create a build configuration from a Meta-Runner. Once the build configuration is created, you can change its steps, adjust parameters and requirements, check how it works, and then extract into a Meta-Runner with the same ID.
Settings in Version Control
The Change log tab listing all changes in the VCS root where project settings are stored has been added to "Versioned Settings" page.
In addition, you can now disable showing settings changes in builds.
New options were introduced for Perforce VCS roots:
- TW-38323 - support for
p4 cleanintroduced in Perforce 2014.1
- TW-37673 - added ability to provide extra p4 sync options, like
- We've added an internal property to avoid clean checkout when Perforce client mapping is modified, please see this comment.
7-zip support for published artifacts
TeamCity can now compress published artifacts to a 7-zip archive:
**/* => dist.7z
As with other supported compression algorithms you can also specify artifact dependency for files inside a 7-zip archive:
Browsing inside 7-zip archives is also supported. But for now we do not support browsing inside 7-zip placed into another 7-zip archive.
Set parameters to dependent builds
If you worked with TeamCity snapshot dependencies, you probably know about dep. parameters. So if the build configuration with ID A has a snapshot dependency on the build configuration with ID B, it can reference B parameter using the syntax:
But sometimes when you start a chain, you want to push a parameter to some or all chain nodes from the top build. It is now possible in this EAP build. With the example above, if you want to start a chain B -> A and push the parameter
param to B, you can add a parameter with the name
dep.B.param to A, either in a custom build dialog or via build configuration parameters. If you want to push parameters to all dependencies, you can use
dep.* in the parameter name:
- fixed issues
- instead of old school DTD files for project configuration files, TeamCity now uses XML schema: http://www.jetbrains.com/teamcity/schemas/9.0/project-config.xsd
- added ability to filter changes by revision on the Change Log page
- removed Java web agent installation package from the distribution
- "Use git alternates" option has been added to Git VCS root settings page (previously was available via a configuration parameter)
- "Use shared mirrors" option has been added to Mercurial VCS root settings page (https://youtrack.jetbrains.com/issue/TW-38557)
- better git/hg progress reporting for agent-side checkout, now all executed commands are shown in a build log