A very early preview: TeamCity Pipelines
Over the past couple of months we’ve been working hard to come up with a new way to work with TeamCity, which we’re calling TeamCity Pipelines. It’s primarily geared toward smaller teams who value a much simpler, more streamlined, pipeline-first UX over the broad feature availability of TeamCity Enterprise. (Yes, it will have dark mode.) You can find out more about it here: https://lp.jetbrains.com/teamcity-pipelines/ We would be grateful if you could take a minute to look at that page and give us your honest feedback, by leaving a comment below. We’d really appreciate your
Kotlin DSL for Beginners: Recommended Refactorings
Imagine you have just switched your TeamCity project over to Kotlin DSL. Your builds run successfully, but what next? What small refactorings can you apply to your Kotlin DSL code to help keep it clean and tidy? In this article, we'll discuss the next steps you can take. 1. Remove disabled build steps, triggers & requirements If you used the UI before switching to Kotlin DSL, there is a significant chance your build scripts contain a fair number of disabled settings, like obsolete build steps, triggers, and requirements. Instead of keeping those settings in your build scripts, let'
CI From The Trenches – Video Interviews
For a while now, we have been getting in touch with TeamCity users to find out about the projects they are working on. From no-code platforms to online games, oil platform management systems to build systems, frameworks to rockets – TeamCity is used in a variety of projects. Now we are posting the interviews so you can get a glimpse into all of these projects. You can discover what they are all about, what languages and frameworks they use, what their build process looks like, what they struggle with, and much more! A big thank you to everyone who took part in our interviews! Enjoy CI From Th
Hardening Your TeamCity Server
TeamCity is at the heart of your build process. It builds your source code into deployable artifacts and often also deploys those artifacts, which means it has potential access to sensitive information. While it offers great security by default, here are some additional steps you can take to harden the security of your build pipelines. General Advice Update your TeamCity server regularly We strongly recommend that you regularly update TeamCity to the latest released version. TeamCity will automatically notify you via the UI once a new update is available. You can also manually check for new
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