![]() In TeamCity, click on “Agents” and then on “Cloud” tab.meanwhile we can configure the could support in the teamcity server.ĬOPY THE AMI ID to the clipboard (looks like ami-a88aa4ce) you’ll see the image pending in the APIs list in the EC2 dashboard.Check the instance of the agent in the EC2 dashboard instance list, and select instance actions->Create Image (EBS AMI).Configure TeamCity EC2 support on TeamCity server.Change config/buildAgent.properties to remove properties: name, serverAddress, authToken (not necessary).Delete " /conf/amazon-*" file (not necessary).Delete content agent logs and temp directories (not necessary).Stop the agent (under Windows stop the service but leave it in Automatic startup type).Remove any temporary/history information in the system.Test the setup by rebooting machine and checking that the agent connects normally to the server.Configure system so that agent it is started on machine boot (and make sure TeamCity server is accessible on machine boot).Next, here is a copy-paste of several steps to take from Once it works, you can take steps to make this image your agent image to be reused.Once the agent is installed, see that the TC server can see it and use it.That way you’ll be able to check their connectivity live before making this machine your official agent image to reuse. Install the agent on he local machine – set it to the IP or DNS of the running TeamCity server.go to the Administration page, and click the upper right link “Install agents”. Now, instead of installing teamcity, browse using the browser to the teamcity homepage (from within the remote machine). downloading VS 2010 from MSDN (2 GB took less than 10 min!) On that machine, I installed what I needed (VS 2010, PostSharp etc.). I selected Instance type – Hihg-CPU medium machine, that is much faster. Repeat steps 1-9, but this time, make sure you select a machine that fits what an agent might do. You should now have a working instance of teamcity. Allocate and set one through the”Elastic IP” link on the EC2 dashboard. I also set an elastic IP for the machine: so I always have the same IP for the machine instance.if you can’t see it, add it or you won’t be able to browse to the machine’s teamcity server home page. Also make sure you can see “HTTP” tcp 80 in that list. source ip is 0.0.0.0/0 (every ip is allowed). To add a rule, click on the empty list under the ‘protocol’ header. Now configure the security group (TC) to enable talking to agents: IN the EC2 dashboard click on “Security Groups” and select your group.I also enabled ports 9090 since I will use this machine to create an agent image later as well. Once you do that, you should be able to see the machine from the outside. To be able to see TeamCity from the outside, you will need to open the advanced firewall settings inside the remote machine, and add incoming and outgoing rules for port 80 (HTTP).I first downloaded chrome and using chrome I downloaded TeamCity. Once you’re inside the instance – you’ll need to open IE (it is in hardened mode so you’ll have to relax its security settings to download stuff).It’s address is a dns address shown below the list under “Public DNS”. ![]() Once you have the password, you will remote desktop (start-run-‘mstsc’) into the instance.You might have to wait about 10 minutes or so for the password to be generated for you. To do that, we’ll get the admin password for that instance: Check it on the list, and click “Instance Actions” - “Get Windows Admin Password”. To do that, you’ll need to Remote desktop into that instance. Now, you need to install stuff on that instance (TeamCity!).Now you’ll be able to see the new instance in the running instances list on your site. Click continue, review and then click “Launch”. ![]() each group is a bunch of settings on which ports can be let through into and out of a hosted machine.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |