TeamCity Cloud 2023.09

Melhora a integração com o Perforce Helix Swarm.
Setembro 22, 2023
Nova versão

Recursos

  • Enhanced Integration with Perforce Helix Swarm - TeamCity can now utilize workflows and tests that already exist in your Swarm setup (instead of creating its own tests). In addition, the Publisher no longer requires credentials of a user with administrator access.
  • Step Statuses and IDs - You can now specify IDs for your steps (similarly to project and configuration IDs). TeamCity uses these IDs to generate new parameters that report the step exit statuses ("success", "failure", or "canceled"). You can use these values to perform custom actions depending on the statuses of previous steps.
  • Additional ReSharper Plugins for the Inspections Runner - The Inspections (ReSharper) runner now features the R# CLT Plugins field that allows you to enter a list of required ReSharper plugins.
  • Service Messages - Added a new service message that allows you to track the contents of the given file and echo new lines to the build log.
  • Token-Based Authentication - Authorization via OAuth tokens has been added for the following:
    • Commit Status Publisher that post statuses to GitLab.
    • Pull Requests features that target GitLab and Bitbucket Cloud repositories.
  • JetBrains Space Integration - Starting with this release, TeamCity build configurations that target JetBrains Space repositories do not require a configured Commit Status Publisher build feature to post build-related updates. Set up a TeamCity project via a predefined Space connection and build statuses will be posted automatically. The option to manually set up the Commit Status Publisher feature is still available for those who wish full control over the process, as well as for custom setups where TeamCity is unable to publish build statuses automatically.
  • Miscellaneous:
    • TeamCity now distributes agents more effectively and processes large build chains with failing builds faster. Starting with this release, dependent builds whose "On failed dependency" condition is "Make build failed to start" no longer wait for an available agent when their dependencies fail or are canceled. Instead, the dependent build's status changes to "Failed to start" as soon as possible, and TeamCity proceeds to the next build in the chain.
    • If users log into TeamCity using credentials of an external 2FA-protected service, TeamCity does not send additional 2FA requests.
    • Performance Monitor now shows absolute values of the consumed/total agent memory.
    • The Dependencies Tab now displays a find panel that allows you to search for specific dependent builds by configuration names.
    • You can now add the dateFormat=<value> parameter to URLs used by your log analysis tools to retrieve build logs.
TeamCity Cloud 2023.09
Perforce Helix Swarm integration

TeamCity Cloud

Crie softwares mais rápido e com menos bugs.

Solicite orçamento Comprar agora

Tem alguma pergunta?

Chat ao vivo com nossos especialistas de licenciamento de JetBrains.