TeamCity Cloud 2022.04.x

Released: Apr 28, 2022

Updates in 2022.04.x

2022.04.4

Updated Sep 19, 2022

Features

  • Referencing parameters as variables is now supported for Approval rules in the Build Approval feature.

Fixes

  • Non-optimal reporting of build statuses in the Commit Status Publisher feature has been fixed.

2022.04.3

Updated Aug 10, 2022

Fixes

  • Previously finished successful test batches are now reused when rerunning a build with the Parallel Tests build feature enabled.
  • Fixed the issue with Commit Status Publisher sending excessive status updates for builds in build chains.

2022.04.2

Updated Jul 13, 2022

Fixes

  • The bundled IntelliJ IDEA has been updated to address the reported Apache software vulnerabilities.
  • Added fixes to the recently released features, such as native Git and parallel tests.

2022.04.1

Updated Jun 1, 2022

Features

  • Added support for recently released Microsoft Visual Studio Build Tools 17.2.0 and Microsoft .NET SDK 6.0.300 installed on TeamCity agents.
  • TeamCity agents now report separate environment variables for Java installations with ARM64 architecture.

Fixes

  • Fixed the problem with adding agents or projects to an agent pool in the classic TeamCity UI.
  • The issue with enabling Native Git operations is now resolved.

2022.04

Updated Apr 28, 2022

Features

  • Improved Speed with Parallel Tests
    • TeamCity is now capable of parallelizing the execution of your tests by intelligently distributing them across multiple build agents, which minimizes their overall duration. This feature takes into account not only the latest run, but also the history of your tests. With that, you can freely refactor your code, break your tests, and do whatever you think is best for your project - without the fear of compromising the parallelization and bogging down your pipelines.
    • Parallelization of test execution can be implemented in a multitude of ways. The easiest way is by using a Maven, Gradle, or Microsoft .NET build runner, as these build runners support this feature straight out of the box. For other build runners and custom build scripts, TeamCity will save the optimal way to parallelize tests in special instruction files, allowing you to set up parallel testing yourself.
  • Built-in Code Quality Inspections for Better Code
    • Starting with this release, you can enable advanced code quality inspections and perform a variety of other new actions – all powered by JetBrains Qodana:
      • Run static analysis checks.
      • Find duplicates in your code.
      • Track how the code quality changes over time, and much more.
    • Adding code inspections to your build pipelines allows you to cut the time you spend on code reviews, ensures maintainability of your projects, and helps every developer on your team to work more efficiently.
  • Taking Cloud Integration to New Heights
    • Migrating build artifacts to Amazon S3 - This release allows you to not only store new build artifacts in Amazon S3, but also move existing artifacts from TeamCity’s local storage to Amazon S3. This is particularly useful for teams who are just starting their migration from a self-hosted setup to a cloud platform and want to take full advantage from the outset.
    • Downloading build artifacts from Amazon CloudFront - This release adds native support for Amazon CloudFront, which allows you to work with artifacts cached on the nearest edge locations provided by AWS. This works on all levels including build agents, web users, API requests, and others.
    • More ways to manage autoscaling at the project level - Storing CI/CD configuration with your project’s codebase is the best way to ensure that it can always be built, tested and deployed. To provide more flexibility when building software in the cloud, this release extends the Kotlin DSL, giving every project the opportunity to have its own Cloud Profile configuration.
  • Powering your Deployment Workflows
    • You can now create build configurations that will not start immediately after being triggered, but will stay queued until everyone from the approval team gives their green light. This feature will be particularly useful for advanced teams that don’t want to limit developers’ ability to access the production environment, but at the same time need a higher level of control over the deployment procedure.
  • Smarter VCS Integrations
    • Space merge requests - Improved the integration with JetBrains Space by adding in support for merge requests. When building an MR, TeamCity will now publish the status to the respective merge request timeline in Space.
    • GitLab issues - Improved the list of supported issue trackers by adding GitLab. This works just as you’d expect: when a commit message mentions an issue ID, TeamCity automatically adds a link to the respective issue in GitLab and displays information about it.
    • Queued builds reporting - Previously, the Commit Status Publisher build feature would not send information to the version control system until TeamCity actually started the build, which was prone to occur long after the commit had been made. Starting with this release, TeamCity updates the commit status immediately after adding the respective build to the queue, providing you with the most up-to-date information. This feature works with all supported VCS services including GitHub, GitLab, Space, Bitbucket and Microsoft Azure DevOps.
    • Running a custom build with a specific revision - When running a custom build, you can now specify an exact revision that may not necessarily belong to the list of changes known by the build configuration. This gives you a lot more flexibility in cases where you want to reproduce historical builds, deploy older versions, debug new build configurations, and many other situations.
  • More Control over Feature Branches
    • With this release, you can improve resource allocation and set this limit on the branch level. For example, your main branch may have an unlimited number of builds that can occupy as many build agents as they need while you limit your feature branches to running just one build at a time.
  • Security: Inside and Outside
    • Log4J and Log4Shell - Although TeamCity has not been affected by the Log4Shell vulnerability, some security scanners wrongly reported it as vulnerable without checking the exact version number of the Log4J framework used in the product. To avoid false-positive scanner reports, Log4J has been upgraded to the latest version.
    • Spring and Spring4Shell - Similarly to Log4Shell, the Spring4Shell vulnerability does not affect TeamCity. However, to avoid false-positive reports from security scanners, the Spring Framework used in TeamCity has been upgraded to the latest version.
  • Harmony with Sakura UI
    • Reimplemented the Agent Pools and Changes pages and vastly improved the overall performance of the new UI.