Skip to main content

Running your build server on Azure

With the first preview of TFS Services(read: Team Foundation Server on Azure), you’re ALM environment in the cloud get’s a lot closer.

But what about my build server? Do I still need to host some servers myself or is their an alternative available?

Although not an official solution (yet), one of the options you have is using an Azure VM Role with a build service, and configure it against your TFS Services instance.

What’s needed to get this working?

First of all you need a Windows Azure account of course. Login to the Windows Azure portal(http://windows.azure.com) and sign up for the VM role beta program(yes it’s still in beta). It can take some time before your subscription is approved so be patient(it took a few weeks before our subscription was activated).

While you are waiting for your subscription approval you can already create the VHD required for your VM role. Follow the steps as described in the following post: http://msdn.microsoft.com/en-us/wazplatformtrainingcourse_vmrolelab_topic2. Replace task 2 with the installation of TFS build Service 11 (Look here for the steps), but only do the installation and skip the configuration part. Replace Task3 and only change the port number in bullet 9 to 9191(This is the default one for the TFS Build Service).

After your subscription is activated you can upload the VHD to Windows Azure(on my slow ADSL connection it took me a few hours). As a final step use the Remote Desktop functionality to connect to the VM Role instance(More info here: http://msdn.microsoft.com/en-us/wazplatformtrainingcourse_vmrolelab_topic3) and configure the build service according to the steps described by Brian Harry.

That’s it!

image

Labels:

Popular posts from this blog

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
Read more