The recording of our recent webinar with Wes Higbee, What’s New in TeamCity 9, is now available on JetBrains YouTube Channel.
In this webinar, Wes goes over the new features of TeamCity 9, namely: rearranging projects with Project Import; storing settings in VCS; creating and editing Custom Charts; running builds in Cloud Agents; as well as some other improvements.
Below are a selection of some of the most frequently asked questions.
Q: When is this feature going to be available with Perforce?
A: We’re considering support for Subversion and Perforce in TeamCity 9.1, but can’t make any guarantees at this point.
Q: What about TFS?
A: TFS might be supported in the future but after Subversion and Perforce.
Q: Given your VCS support priorities for new features, are Git, Mercurial and TFS your recommended VCS combinations with TeamCity?
A: Apart from storing settings in VCS, Git, Mercurial, Subversion and Perforce, they are all supported greatly with TFS catching up. CVS, Vault and ClearCase support can be a bit limited.
Q: How does TeamCtiy handle it if somebody corrupts the configuration in the repository?
A: If there are errors while applying changes then TeamCity will not change project settings and will show an error.
Q: Is it possible to use branches, e.g. to test a change in the build configuration before making it productive?
A: Not yet, but we definitely want to add this feature.
Q: How does the VCS know which branch to use?
A: It uses default branch specified in VCS root.
Q: If you want to revert to an earlier version, you need to find the desired version from within the version control system. That is, there’s no GUI way to see the previous version from TeamCity perspective?
A: There is a changelog tab where you can see all the changes.
Q: What about parameters? Are they synced too? If not, the new features could replace templates, couldn’t they?
A: All the settings are synced form the VCS as if you edit the settings right in the TeamCity data directory (or change them in UI).
Q: If a have sync on the root project, are all sub-projects synced too? Is it recommended to have VCS for the sub projects, or a VCS for the root project only? Or are both recommended?
A: By default sub projects will be placed into the same version control. If you don’t want it for some projects, you can disable synchronization in them.
Q: Can I import a TC8 backup in TC9? It would make testing easier
A: No, both servers should have the same version. 9.0 and 9.0.x are compatible, but 8.1 and 9.0 not.
Q: How does that work out with the licensing system? I guess the number of agents licensed its the hard limit of active agents, including from the cloud?
A: Yes. The total number of agents (real and virtual) connected at any given time should not exceed the total agent licenses limit. When there are enough agent licences, TeamCity automatically authorizes new cloud agents and unauthorizes the stopped ones.
Q: How do we create the VM image?Is a build image template available for the Azure VM image?
A: There are no templates with TeamCity agents for now
Q: Can we configure the “on-demand” agents to use the same VM with more than one agent, until that max out? i.e. 3 agents per Azure VM.
A: TeamCity assumes there is a single agent per instance. The recommended setup is to have a single agent per machine.
Q: Can the on-demand agents be used with on-premise vCenter?
A: Yes we have vSphere plugin doing the same.
Q: Does the agent spun up hang around for a while or is it immediately removed?
A: There is an idle timeout setting to shutdown the agent instance after. When stopped, the agent is deleted from TeamCity list of agents.
Q: EC2 cloud agents auto-shutdown policy is not the best it could be meaning that it doesn’t take into account that you always get charged for an hour of usage of an EC2 instance. Any plans to improve this?
A: Yes, we do have plans to adjust the shut down to the hour limit. You are welcome to vote for https://youtrack.jetbrains.com/issue/TW-9680.
Q: Is it possible to have time instead of build number on the X axis?
A: No, this is not possible
Q: I have a configuration that has different snapshot dependencies, is there any way to show the build time from beginning to end, meaning when the first dependency run to the end?
A: No, statistics charts operate per build. Theoretically you can calculate this time and report it as statistic value in the last build of the chain.
Q: Can you export the stats data?
A: Yes, there is a “download” action on the chart. Also available via REST API.
Q: Does TeamCity have possibility to show charts with time that took to run every test?
A: On the build’s Tests tab, you can see the duration chart for each test. As well on the Test history page.