Choose a Build Agent to Run Your Personal Build
When running your builds, TeamCity selects between the build agents taking into account a whole set of different factors and parameters. First and foremost, it tries to run the build on the fastest available build agent based on builds history of a build configuration on this agent. And since the available build runners depend on environment where the agent is running, TeamCity chooses an agent having required a build runner.
Until recently it was possible to run the build on desired build agent only from the web interface by, for example, clicking the Run button and selecting the desired agent from the list. The Run configuration policy, which we have told you some time ago, allows to make TeamCity create builds of some build configurations only on specific build agents. As a result, TeamCity will create builds of the build configuration only on specific build agents no matter if they are initiated:
- manually (either from the web interface or using the pre-tested commit)
- automatically when the changes appear in the version control system
- periodically (a time-based trigger is enabled)
With TeamCity plugin for IntelliJ IDEA you can now opt to select one or several build agents to run your personal build on. Such approach allows you to test your changes with more granularly under:
- desired platforms,
- operating systems,
- environment variables.
which are specified for the build agent available in your company’s build grid:
The latest builds with the updated IntelliJ IDEA plugin are available at our EAP page.
We hope you will greatly enjoy the feature and use it on a daily basis.
Subscribe to Blog updates
Thanks, we've got you!
Introducing AWS Connection: A New Approach for Working With AWS in TeamCity
We’ve introduced a new feature called the AWS Connection, which makes it possible to work with AWS credentials more flexibly and safely.
TeamCity 2022.10: Sakura UI, Improved Integration With Amazon AWS, Out-of-the-Box HTTPS Support, Google OAuth Authentication, and More.
TeamCity 2022.10 comes with the Sakura UI enabled by default, introduces many cloud-related features including the AWS credentials management system and out-of-the-box terminal access to AWS EC2-based build agents, and adds important improvements to VCS integrations. Server administrators will love the new streamlined way to implement HTTPS for on-premises TeamCity installations. Also, a new authentication module for using Google accounts and a number of long-requested features have been implemented.
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 …
TeamCity 2022.04: Parallel Tests, Improved Integration with Amazon AWS, Built-in Code Quality Analysis, Updated VCS Integrations, and more
TeamCity 2022.04 introduces the new Parallel Tests feature that delivers an extraordinary speed boost when testing your projects. New powerful code analysis features will cut the time you spend on code reviews and increase the maintainability of your projects. Users who run their builds in the cloud…