Type the name for your build configuration. Next, create a new project by clicking Projects link (top menu).Ĭhoose “From a repository URL” and paste the link into your repository. Click the “Agents” link (top menu), go to Unauthorized, click on the agent from a list, and click "Authorize Agent" button. Once TeamCity is running, configure an Agent. Go through the simple steps to configure TeamCity. This will pull the images and start TeamCity on localhost:8111.
- teamcity-server-datadir:/data/teamcity_server/datadir.
This ensures that only TeamCity will be able to use the specified IAM role.Įnable this option to automatically find access keys according to the default chain.Įnter an ID of your registry or AWS account. We strongly recommend that you always define it when using temporary credentials. You need to create this role in advance in your AWS console and assign it to all the necessary permissions. Specify a role to be used for generating temporary credentials. Such credentials are short-term and do not belong to a specific user. Temporary credentials: get temporary access keys via AWS STS. You can find them in the Identity and Access Management section of your AWS console. Select an AWS region where the target resources are located.Īccess key: select to use preconfigured AWS account access keys. For this, such a connection needs to be selected when adding a Docker Support feature to a build configuration. Amazon ECRĪ connection to Amazon Elastic Container Registry (ECR) allows storing Docker images in private AWS registries.
#Teamcity agent docker how to
See also how to use this functionality to double the number of pulls allowed to a Free Docker Hub user profile. Automatic logout will be performed after the build finishes. If you need to log in to a registry requiring authentication before a build, select the corresponding option and a connection to Docker configured in the Project Settings. If your docker daemon uses a non-standard location for the images/containers, the location can be specified using configuration parameter, preferably in buildAgent.properties file. The location is important, as the Free disk space feature analyzes which disk volumes should be cleaned for the build. The Docker Support assumes, that docker images are stored under Clean-up of Images on Build AgentĪs part of Free disk space build feature, Docker Support cleans up images which were created by TeamCity builds on this build agent. When the server clean-up is run and it deletes the build, all the configured connections are searched for the address of this registry, and the images published by the build are cleaned up using the credentials specified in the found connection. It works as follows: when an image is published, TeamCity stores the information about the registry of the images published by the build. You can select the corresponding option and instruct TeamCity to remove the images published by a certain build when the build itself is cleaned up.
If you have a build configuration which publishes images, you need to remove them at some point. Docker Images Clean-up Clean-up of the Pushed Images
#Teamcity agent docker software
Refer to this page for information on software requirements, supported environments, and other common aspects of this integration. These two options require configuring a connection to a Docker registry:ĭocker Support is a part of the TeamCity-Docker integration toolset. The tab provides information on Docker-related operations.Īutomatically log in to an authenticated registry before the build and log out of it after the build. The Docker Support build feature allows automatically signing in to a Docker registry before the build start.Įnables the Docker events' monitoring: such operations as docker pull and docker run will be detected by TeamCity Īdds the Docker Info tab to the Build Results page.
0 kommentar(er)
