![]() On the first page, we can configure basic settings for our machine. On the next screen, we can configure our virtual machine. Feel free to choose a Windows Server 2016 operating system if you would like to. Click on it.įor this article, I decided to use a virtual machine running “Windows Server 2012 R2 Datacenter”. Luckily Microsoft has a set of recommended resources where “Windows Server” is listed in the first place. Azure has grown huge so if you type “Windows 2012 R2” you’ll still get many results. There is a friendly filter box where we can filter all the resources available to us. Let’s create a new resource by clicking on the green plus in the left corner of the screen. The first page you’ll see is the dashboard which holds all the important resources you already have. Log in to the Azure portal using your credentials. Let’s jump right into the Azure portal and create our Virtual machine. Please write a comment below this article if you would like to read a Linux version of this article. If you install TeamCity on a Linux machine the installation and configuration might be slightly different. ![]() Or if cost is important to you I would choose Linux because it is a lot cheaper than the Windows based Virtual Machines. If you are not sure which operating system you should use, I would choose the operating system you are more familiar with. Those applications are made for Windows and I want to be able to build them on a Windows machine. The most important reason why I decided to use Windows Server as the operating system is that I want to be able to build. If you only want to build software that (also) builds on Linux, feel free to install TeamCity on a Linux server machine. That’s a pretty cool experience by the way! Choosing an operating systemįor this article, I used Windows Server 2012 as the operating system. The Azure portal has a simple wizard which helps us setting up everything we need at once. In the instructions below I create a storage account while creating the Virtual Machine. We need a storage account which can be attached to the Virtual Machine. If you think like me, you will ask what about the hard-drive? Azure has a model where the storage is paid separated from the Virtual Machine. The cost associated to the Virtual Machine is based upon RAM and CPU usage. Because we want it to run in the cloud and I like the Azure ecosystem we need a Microsoft Azure Virtual Machine. TeamCity needs to run on some infrastructure. We want to run TeamCity for our continuous integration builds. I think it is important to understand what we build. We need to configure TeamCity according to our needs.We need to install TeamCity on the Virtual Machine.I go step-by-step through this as I want to prevent you from setting up the machine over and over again. We need to create a Virtual Machine in the Microsoft Azure portal.(If your company is a Microsoft partner or has an MSDN subscription you might have free credits to spend each month. If you don’t have an account, you should immediately create one. You need to have access to the Microsoft Azure portal.The following steps are required to setup TeamCity on an Azure Virtual Machine: I will tell you how I setup a continuous integration and continuous delivery system for all my applications including many different types of applications such as ASP.NET Web applications, Angular applications, ASP.NET Core applications and Android applications. I want to write code and therefore I would like to deal with my infrastructure as less as possible. ![]() It is neither fun nor fool-proof.Īnd hey, I am a software developer. I don’t like doing the same steps all over again. This particular article is focused on the installation of JetBrain’s TeamCity as a continuous integration software on an Azure Virtual Machine and its basic configuration.Īre you a friend of automation? Are you tired of doing the same thing over and over again? Great! Me too.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |