Simplified plugin management
TeamCity provides means of extending its functionality with more than 350 external plugins featured in the JetBrains plugin repository.
Before this EAP, you needed to install new plugins manually and then restart the server. Updating the installed plugin was done in a similar way.
This EAP provides simplified plugin management:
You can now upload / install new TeamCity plugins directly from the JetBrains plugin repository (in addition to the existing ability to install plugins manually).
No server restart required for the new plugins installed either from the plugin repository or manually.
Updating an installed plugin can now be done via the TeamCity Web UI. If automatic checking for the plugin updates is enabled, TeamCity will perform it on the server start and then every 24 hours. You can also check for updates manually. At the moment you still need to restart TeamCity for the update to take effect.
Development of reloadable plugins
Developing plugins for TeamCity is now easier, as you do not need to restart the development server when deploying your plugin or its updates.
Enforced build steps and build requirements in project template
TeamCity lets you create a project template to be used by all build configurations and subprojects in the project hierarchy. Then the project users can redefine the template settings in their configurations. But if the project administrator wants to to enforce some settings on all the build configurations in the project so that other users could not redefine them, there is the ability to select the enforced settings template for the project.
Prior to this EAP, you could enforce build features, options, and parameters. Now it is also possible to enforce build steps and build requirements.
Bundled Pull Requests plugin
Some time ago we announced the TeamCity pull requests plugin, which is now bundled and available as a build feature.
The GitHub pull requests build feature lets you automatically load GitHub pull requests information and run builds on pull request branches. You no longer need to provide a VCS root branch specification like refs/pull/*/head. Moreover, pull requests can be filtered by target branch as well as by author. You can choose to build
- PRs coming from the members of the same organization only
- PRs from the members and all external collaborators
- PRs from everybody
After a build is run on a pull request, TeamCity will provide additional details for the pull request branch on the build overview page:
TeamCity now uses HSQL 2.4.1 as the default internal database.
The bundled .NET Tools (dotCover and ReSharper CLT) have been upgraded to the latest released version, 2018.1.4
TeamCity built-in NuGet feed supports references for per-project feeds
- All fixed issues