Child pages
  • Hajipur 9.0 EAP3 (build 31886) Release Notes

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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 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.

...

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>/config/projects/<ProjectID>/pluginData/plugin-settings.xml file. now Now you can create a new chart:

...

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 , can 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 it's stepits 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 TeamCity settings are stored has been added to "Versioned Settings" page.
!screenshot!

...

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:
dist.7z!folder/**

...

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:
dep.B.<parameter name>

But sometimes when you start a chain, you want to push a parameter to some or all chain nodes from the top build. It becomes 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: dep.*.param.

...

  • 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 added 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)