TeamCity 2020.1

ビルドステップに実行条件を設定可能
5月 19, 2020 - 14:30
新バージョン

特徴

  • Conditional build steps - TeamCity 2020.1 allows you to specify conditions for your build steps and execute them only if the criteria are met.
  • Build with scale in a cluster - Simple and reproducible cluster deployments are now available out of the box. TeamCity 2020.1 lets you implement a scalable CI/CD architecture on top of Kubernetes: build agents can be launched automatically when you need them, do their job, and then be removed after the build is completed.
  • Multi-server - Running multiple TeamCity servers and making them work together can elevate your CI/CD to a whole new level of performance and reliability. This release has improved how TeamCity works in a clustering environment by extending the capabilities of secondary servers with trigger processing and support for user-level actions in the UI.
  • Trigger processing - Professionals working with large installations have hundreds if not thousands of triggers that fire on changes in VCS, package updates, and new artifacts. To help them achieve the highest possible performance, we now allow secondary servers to take part in this process and take some load off the primary server.
  • User-level actions - This release improves the UI of the secondary server, making it possible to modify user profiles, change view of projects and configurations, manage build agents, and more.
  • Easier deployment of cloud build agents - TeamCity 2020.1 comes with a new option to download a pre-packaged agent distribution from the TeamCity server. Pre-packaged build agents don’t need to update themselves upon connection to the TeamCity server, and this makes creating and updating cloud images faster and more straightforward.
  • Notifications - New build feature allows project administrators to set up automatic alerts to the entire team. New notifications can be configured on the build configuration level, so you can edit, reuse, and share them using the Kotlin DSL. The all-new Slack notifier lets your team get notifications about the status of your builds directly in Slack.
  • Jira Software Cloud - TeamCity has always had elegant integration with Jira, which automatically replaces issue codes in commit messages with links to the respective Jira issues. To support even more workflows, this release has extended the integration and started to send the status of your builds and deployments to Jira Software Cloud. Now you can look into your CI/CD pipelines and release history right in your issue tracker, and see which issues are associated with failing builds.
  • Microsoft Azure DevOps - This release extends the list of Git hosting services supported by the Pull Requests build feature, and adds support for the Azure DevOps pull requests. The new option allows you to automatically run builds on pull request branches of the Azure DevOps, similarly to how you can do it with GitHub and GitLab.
  • New Sakura UI - To support more use cases of the classic TeamCity, the experimental UI of version 2020.1 comes with updated Agents and Projects pages, and allows configuring the project sidebar.
Adds support for conditional build steps

TeamCity(英語版)

継続的な統合とビルド管理のソリューション

ご質問がありますか?

今すぐ JetBrains ライセンススペシャリストとライブ チャット