New in TeamCity 2020.2: Short-Lived Access Tokens
TeamCity 2020.2 now supports short-lived access tokens, which can expire automatically after a specified time period. They are perfect for shareable command-line scripts or demos, when you don’t want to remember to go back to the UI to delete your token. Watch the feature in action: For more details on how TeamCity’s access tokens work, have a look at our documentation.
New in TeamCity 2020.2: Bitbucket Cloud Pull Requests
TeamCity 2020.2 finally comes with integration for Bitbucket Cloud pull requests. You can set up TeamCity to automatically detect pull requests made in your Bitbucket Cloud repository and run builds for them. Together with the Commit Status Publisher and the Automatic Merge build features, this makes working with pull requests in Bitbucket Cloud really easy. Watch this screencast to see the “Bitbucket Cloud Pull Request” feature in action. For more details on how TeamCity’s pull request support works, have a look at our documentation.
New in TeamCity 2020.2: Python Build Runner
TeamCity 2020.2 comes with first-class native Python Support, and you no longer need to use a third-party plugin to build your Python projects. It supports all popular Python build workflows: Run files, modules, or custom scripts. Execute pytests or unittests. Run linters, like flake8 or pylint. Use virtual environments, like virtualenv or pipenv. Run your Python builds inside a Docker container. Use Kotlin DSL to configure your Python build steps. In addition, the Python runner integrates tightly with TeamCity just like all other TeamCity runners. You can track changes, analyze failures, a
New in TeamCity 2020.2: Agentless Build Steps
TeamCity 2020.2 comes with an exciting new feature called “agentless build steps”. It is useful whenever you want to call an external service during your builds that does not respond immediately, but takes an indefinite amount of time to run. Examples could be 3rd party deployment services, scripts running on your servers to prepare environments, or services used for manual QA verifications and deployment approvals. Before TeamCity 2020.2, such calls would block your build agent while it was waiting for the response from the service. With “agentless build steps” you can now reuse the agent fo