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:
roles-config.xmlor groups with the same keys have different set of roles granted)
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.
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:
Modifying custom charts now can also be easily done from the TeamCity Web UI.
More details on this feature are available in our documentation.
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.
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:
p4 cleanintroduced in Perforce 2014.1
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.
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: