Running AWS EC2 spot instance build agents using a spot placement score Got a question or comment? Feel free to leave your feedback in this YouTrack issue. Thanks to this feature, your builds will run uninterrupted as long as there are available machines within the indicated tags. If this machine is unavailable, TeamCity will switch to the next available option, and so on. This way, TeamCity will automatically find the most suitable available machine and spin up the agent. If you have a Mac instance type selected, you can now set tags to indicate the bare metal machines that you’ve reserved in AWS for TeamCity to run your agents. TeamCity now uses tags to find a suitable dedicated Mac host to run instances. If you’re using EC2 Mac instances, you have to run builds on a specific bare metal machine. Got a question or comment? Share your feedback on this feature in this YouTrack issue. This way, you can save a significant amount of time on maintenance. This means that, if you update the image, it will automatically be used by all compatible project/build configurations. You can now reference the latest created AMI with a given tag value or combination. If there were many cloud profiles that used the same image, and you updated it, you’d have to go and manually update the ID in each of those cloud profiles. Previously, all of these cloud images would have to be updated manually in case this custom image is updated, as the AMI ID will also change. This image can be referenced by a unique AMI ID and reused by multiple build configurations. Suppose you’re using a custom image for running your build agents. In TeamCity Cloud 2023.07, we’re also introducing the ability to configure the build agent to launch an instance from the last created AMI with a given tag value. Configuring agent image to launch an instance from the last created AMI with a given tag value Share your feedback on the feature in this YouTrack issue. In addition to that, you can also select several instance types and security groups in TeamCity. It also simplifies the setup of cloud profiles: now, you don’t need to set up multiple cloud images just to achieve a regional scale and instance type diversity. In case the selected subnet or instance type runs out of capacity, TeamCity will automatically switch to the second available option, and so on. TeamCity can now take the first option from the available combination and run an instance. Running an instance in a specific region instead of a particular subnet would make more sense, as this way, TeamCity can choose the most appropriate subnet in terms of available resources.Ī combination of running instances in the scope of a region as well as using a few instance types, gives you more reliable instance usage. However, we realized that in most cases, users didn’t want to be restricted to just that one subnet. Previously, when setting up an EC2 cloud image in TeamCity, you could only select a single subnet for your virtual private cloud. EC2 updates Specifying multiple subnets and instance types for EC2 cloud images Let’s take a closer look at each one of these features. TeamCity now supports refreshable tokens for Space and brings a new type of connection on the project level with Space. In addition to the EC2 support improvements, we’re introducing the updated TeamCity and JetBrains Space integration. The new TeamCity Cloud 2023.07 comes with major cloud profile enhancements that include a completely revamped UI for cloud profile configuration, the ability to specify multiple subnets, and support for EC2 Mac instances, among other things.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |