TeamCity 2020.2

Integriert Python-Build Runner und eine Funktion zum Anzeigen der Festplattennutzung in externen Speicherorten.
November 24, 2020
Neue Version

Funktionen

  • Added support for authentication using external services: GitHub, GitLab, and Bitbucket.
    • You can instantly match external OAuth accounts with existing TeamCity users, and let them work with their projects without having to enter a password.
    • Added the ability to integrate with user directory features of the supported services, such as GitHub organizations and GitLab groups, and can automatically create new profiles when new members join your team.
    • Added support for on-premise installations of GitHub (GitHub Enterprise) and GitLab (GitLab self-hosted).
  • Improved integration with Bitbucket Cloud by adding support for pull requests.
    • You can now set up TeamCity to automatically pick up pull requests made in your Bitbucket Cloud repository and run the respective builds.
  • Added new Python build runner which enables you to use TeamCity in your Python projects.
    • The new build runner works with all operating systems, supports virtual environments, and integrates with all common testing frameworks and code inspection tools for Python.
    • The results of your Python builds and tests are reported in the TeamCity UI, in the same way as with all other TeamCity build runners. You can track changes, analyze failures, assign investigations, and use all the other TeamCity features currently available.
  • Jetbrains Space is now supported by the Commit Status Publisher feature.
    • Commit Status Publisher will now automatically send the status of your builds to Space, letting you see it on the Commits page of your project.
  • Your builds can now execute their final steps in agentless mode, releasing the build agents and allowing them to run other queued tasks.
    • TeamCity displays agentless build steps as standard builds and will enable you to track their status, browse their logs, and view their history.
  • Added the ability to edit project-level settings in secondary servers. This enables your team to set up new builds while the primary server is under maintenance.
  • Added the ability to see the disk space occupied by builds not only on your local drives but also in remote locations.
  • You can now customize the clean-up schedule with the use of cron-like expressions to have the server cleanup start at regular intervals.
  • Improved the Build Dependencies page:
    • The Timeline view now shows not only started and finished builds but also queued builds.
    • The Build Chain view now shows the “right” part of the chain: all builds that depend on the current one.
  • Added new Test History page to the Sakura UI. The new page gives you detailed information on your tests and allows you to analyze trends, see investigation history, and more.
  • Added the ability to search the build log.
  • Sakura UI plugin development framework: Added a new way to write and integrate plugins for the user interface.
  • Added a new Build Queue page which lets you quickly see the changes for every queued build, understand what triggered the build and where it will run, get the estimated time when it will start, and view all the other build information in a neat and convenient UI.
    • You can select any builds that you don’t need and remove them from the queue, or alternatively, if there are builds that need to complete sooner, you can move them to the top of the list.
Disk usage monitor

TeamCity On-Premises

Eine Lösung für die kontinuierliche Integration und das Build-Management.

Sie haben eine Frage?

Live-Chat mit unseren JetBrains-Lizenzierungs-Spezialisten.