Transition to native Git in TeamCity 2022.04 brings 10x fetch time reduction to IntelliJ Platform
Starting from version 2022.04, TeamCity switched to native Git on the server side for Git VCS connections. The switch should positively impact both performance and overall experience of working with Git repositories on the TeamCity server side.In this blog post, we’ll talk about the reasons for the switch and our own experience with this feature. Background In the case of the agent-side checkout, TeamCity agents have always been using a native Git executable to checkout sources. This functionality spawns a separate process for native Git commands like ls-remote, fetch, checkout, and othe
Building GitHub pull requests with TeamCity
The support for pull requests in TeamCity was first implemented for GitHub as an external plugin. Starting with TeamCity version 2018.2 the plugin is bundled in the distribution package with no need to install the external plugin. The functionality has since been extended in version 2019.1 to support GitLab and BitBucket Server. In this blog post, we will share some tips for building GitHub pull requests in TeamCity. First, there are a few things you need to know about when configuring the VCS root in regards to pull request handling. Next, we’ll cover Pull Requests and the Commit Status Publ
GitHub Pull Requests plugin for TeamCity
The hassle with Pull Requests These days pull requests is a common technique of accepting changes from third-party contributors. In fact, it proved to be so convenient that some companies started to use it even for their regular development workflows. It is possible to configure TeamCity to run builds on GitHub pull request branches. One had to provide a VCS root branch specification like refs/pull/*/head for that. However, this configuration is not without its downsides. For instance, with this configuration, the pull request for TeamCity is just a branch in a Git repository. It means that
Automatically Building Pull Requests from GitHub
Scenario You're running an OSS project* and someone makes a pull request. You've got two choices: Merge and Pray Pull to local branch, build, run tests and merge if all OK What do you do? Well, what is it going to be? I know what I'd like to do, and GitHub makes it so so tempting: But unfortunately I go with the second option. That's a pain, specially if you do a quick code-review and things look decent. Yet you still need to make sure that it builds and all tests pass. Well there is a third way. And what's even nicer, is that it's also possible with TeamCity. *Thi
TeamCity 7.1: Control the flow!
We're happy to tell you that TeamCity 7.1 is officially released! If you were following the early access program, you may have noticed that in this release we were mostly focusing on enhancing support for distributed version control systems, such as Git and Mercurial, making the daily work with branches smooth, clear and easy. So give a warm welcome to Feature Branches in TeamCity and check them out! As you know, Feature Branches in DVCSs like Git and Mercurial allow you to work on a feature independently from the repository and commit all the changes for the feature onto the branch, merging
TeamCity 7.1 EAP (build 23833)
Today's EAP build is all about significant improvements in Feature Branches support. Since the release date approaches, we're focusing on polishing already introduced features and fixing known issues. Here's what we have for you this time: Extended branches specification syntax: When you describe branch specification, you now have more control on what will be shown as a branch label in TeamCity UI. For instance, type something like this: +:refs/heads/release-(7.0) +:refs/heads/release-(7.1) TeamCity will use label 7.0 for builds from refs/heads/release-7.0 branch and 7.1 for builds from ref
Another update for TeamCity is now available - TeamCity 5.1.2, which might be especially interesting for those who use Git with ssh protocol or Visual Studio add-in. This version contains a number of improvements and fixes in these areas and is considered to be more stable; plus, it includes some other fixes. See the complete list of changes, download the build and share your feedback with us. Do not forget to backup your data before upgrading. The JetBrains TeamCity Team
A fresh update for TeamCity is now available - TeamCity 5.1.1. Since this release, the Check out on agent feature has become available for Git. Furthermore, a number of bug-fixes included. Take a look at the release notes, download the build and tell us what you think. Don't forget to back up your TeamCity data before upgrading to a new version - just to be on the safe side. Sincerely, JetBrains TeamCity team.