![]() ![]() The default agent runs as a separate container on the same instance. ![]() The TeamCity server runs on an EC2 instance with CoreOS Container Linux. Just generate the root account and it’s ready to use. ![]() Once the deployment is ready, you will see the TeamCity server endpoint in the Output section which points you to your TeamCity installation. It takes about 15 minutes for the template to deploy the whole stack, the most time-consuming task being the RDS Database instance roll up. The template provides several parameters: The stack can be launched via the ‘Run on AWS’ button available on the TeamCity site. The template is located in the S3 bucket. And should you decide to destroy the stack, CloudFormation also provides a super simple way to do it with just one click. Using this template lets you run all the above steps with just a single click. We have tried to ease this process and created an official CloudFormation template to run the TeamCity stack in AWS. Configuring it to then connect to the database,Īnd then making the whole installation secure requires even more effort.Configuring the EC2 instance to run a TeamCity server,.Usually, installing TeamCity on top of AWS is quite a time-consuming task. In this post, we will go over what’s under the hood of the template, and why it may save you some time and effort. This lets you run TeamCity in AWS using the official CloudFormation template. The default value is 1000.As you might have noticed, there was recently an option added to the Get TeamCity page of our website: AWS. 3.upload.retryDelayMs - the initial delay between attempts in milliseconds. 3.upload.numberOfRetries - the number of attempts the tool makes when uploading data to S3 if it encounters errors. 3.forceVirtualHostAddressing - specifies whether the tool should use the virtual hosted style of S3 URL addresses instead of the deprecated path style. 3.threadCount - the number of threads that the tool should use to upload data to S3. It may happen due to the lack of permissions. controls whether the migration should fail if the tool cannot fetch the storage settings from the TeamCity server. threadCount - the number of threads that the tool should use for processing. You can add the following properties to the configuration file. Migrate.bat -project="SampleProject" -source="PROJECT_EXT_2" -start-migration -remove-artifacts-in-source reset-migration-plan - discard the current migration plan.įor example, the following command moves artifacts from the given Amazon S3 storage to a currently active storage. Artifacts that were not copied will not be removed. remove-artifacts-in-source - delete copied artifacts from the source storage. revert-migration - remove copied artifacts from the target storage in case of an incomplete or interrupted migration. start-migration - copy artifacts from the source storage to the target storage. show-migration-plan - show the migration plan. create-migration-plan - create or update the migration plan. ![]() To migrate artifacts in one go (without the tool asking you for confirmation or input), specify the required migration steps by adding the following commands. Use this option to discard the saved migration plan if you specified incorrect migration parameters. You can select this option in case of an incomplete or interrupted migration.ĭelete artifacts from the source storage.įorget the migration plan. This option removes copied artifacts from the target storage. The first time you run the migration tool in this mode, it detects artifacts that should be copied, saves the migration plan, and asks you for the next step.Ĭopy artifacts from the source storage to the target storage. Migrate.bat -p "NetFrameworkProject3" -source="PROJECT_EXT_2"Ĭurrently, the tool accepts only Amazon S3 bucket IDs as the "source" parameter values. The snippet below demonstrates the contents of a sample application.properties file. The server URL and default artifact storage paths can be found on the Administration | Global Settings page. Navigate to Your Profile | Access Tokens to create a new token. Tokens must have permissions sufficient to access artifact storages. token - the TeamCity authentication token. If your TeamCity server uses multiple directories as artifacts storages, use a semicolon character ( ) as a separator. directories - the absolute path to the local TeamCity artifact storage. the TeamCity server's address (protocol, host, and port). Configuration Fileīefore you can run the artifacts migration tool, you need to specify the following settings in the config/application.properties file. Note that you need this tool to be on the same machine where the TeamCity server is installed. You can download this tool from the Project Settings | Artifacts Storage page. The artifacts migration tool is a command-line tool that allows you to transfer build artifacts from one storage to another.Ĭurrently, the tool accepts only Amazon S3 as a migration target. ![]()
0 Comments
Leave a Reply. |