TeamCity agent should start on machine startup.TeamCity agent should be correctly installed.Here are the requirements for an image that can be used for TeamCity cloud integration: Preparing Image with Installed TeamCity Agent View information on example policies for Linux and Windows on the Amazon website. See the section below for permissions to set IAM roles on an agent instance. To launch an instance with Iam Role (applicable to instances cloned from AMI-s only) the following additional permissions are required:Īn example of custom IAM policy definition (allows all ec2 operations from a specified IP address): To use spot instances, the following additional permissions are required: TeamCity requires the following permissions for Amazon EC2 Resources: If you need TeamCity to use proxy to access EC2 services, please read on a current workaround in the dedicated issue. Please ensure that the server URL specified on Global Settings page in Administration area is correct since agents will use it to connect to the server. Please note that the number of EC2 agents is limited by the total number of agent licenses you have in TeamCity. configuring EC2 integration on TeamCity server.preparing an Amazon EC2 image (AMI) with an installed TeamCity agent.Understanding Amazon EC2 and ability to perform EC2 tasks is a prerequisite for configuring and using TeamCity Amazon EC2 integration. On instance terminating/stopping, its disconnected agent is removed from authorized agents list and is deleted from the system.Īmazon EC2 Spot Instances are supported. If an EBS-based instance id is specified in the images list, the instance is stopped instead. If running timeout is configured on the cloud profile and it is reached, the instance is terminated. After that the agent is processed as a regular agent. Once an agent is connected from a cloud instance started by TeamCity, it is automatically authorized (provided there are available agent licenses). TeamCity ensures that the running instances limit configured in the cloud profile is not exceeded. If there are no usual agents available, TeamCity finds a matching cloud image with a compatible agent and starts a new instance for the image. Once the agents are connected, TeamCity stores their parameters to be able to correctly process build configurations-to-agents compatibility.įor each queued build, TeamCity first tries to start it on one of the regular, non-cloud agents. Once a cloud profile is configured in TeamCity with one or several images, TeamCity does a test start for all the new images to learn about the agents configured on them. It is assumed that the machine images are pre-configured to start TeamCity agent on boot (see details below). Sharing single EBS instance between several TeamCity servers.Tagging for TeamCity-launched instances.Configuring a cloud profile in TeamCity.Preparing Image with Installed TeamCity Agent.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |