Skip to main content

Adding a build agent to TFS 2015

By
I was shocked how simple we can create and attach a new build agent to TFS 2015. There are only a few simple and small steps that we need to do.
The new build system that comes with TFS 2015 and Visual Studio Team Services (Visual Studio Online) is not using anymore the old and classic XAML build definition. The new one allows you to define the build as a flow of events where you can specify at each step what do you want to happen. This is done easily  directly from the web portal.

If you need to create or add a new build agent to your TFS 2015 infrastructure, than you will be shocked how easily this can be done.
First step is to download from the "Agent Pools" tab the agent.
Once you done this step, you will need to run the executable on the machine that will become the new Build Agent. I recommend to run the executable file from a command prompt and provide all the information that are required. You only need to know the TFS 2015 address and to have access to TFS as "Agent Pool Service Account".
And we are done!

You will find out that you cannot run the build directly. This will happen because you will need to install the application that are needed by your build (msbuild, visualstudio, vstest). The error that is displayed when you didn't install all that you need looks like the one below.
"No agent found in pool 1 which satisfies the specified demands"

Don't worry. The installation of all this dependencies is smooth and you don't need to do any kind of custom confirmation.

A good MSDN starting point: https://msdn.microsoft.com/en-us/Library/vs/alm/Build/agents/admin?f=255&MSPPError=-2147217396

Labels:

Comments

Post a Comment

Popular posts from this blog

How to audit an Azure Cosmos DB

By
In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...
Post a Comment
Read more

Why Database Modernization Matters for AI

By
  When companies transition to the cloud, they typically begin with applications and virtual machines, which is often the easier part of the process. The actual complexity arises later when databases are moved. To save time and effort, cloud adoption is more of a cloud migration in an IaaS manner, fulfilling current, but not future needs. Even organisations that are already in the cloud find that their databases, although “migrated,” are not genuinely modernised. This disparity becomes particularly evident when they begin to explore AI technologies. Understanding Modernisation Beyond Migration Database modernisation is distinct from merely relocating an outdated database to Azure. It's about making your data layer ready for future needs, like automation, real-time analytics, and AI capabilities. AI needs high throughput, which can be achieved using native DB cloud capabilities. When your database runs in a traditional setup (even hosted in the cloud), in that case, you will enc...
Post a Comment
Read more

Azure Service Bus - How to extend the lock of a message | RenewLock

By
In this post we will discuss about Azure Service Bus Topics and Queues, with a special focus on Peek and Lock feature. Introduction Azure Service Bus is a messaging system that allows us to send messages between different systems in a reliable and easy way. A lot of concepts from ESB are implemented by Service Bus, allowing us to do do magic stuff with messages. There are two ways to consume messages from Service Bus Peek and Lock - locks a message for a specific time internal and notify Service Bus when we want to mark the message as processed (removed from Service Bus) Receive and Delete  - once a message is received from Service Bus, it is also deleted automatically from the messaging system Peek and Lock When using Peek and Lock, by default we lock the message for 60 seconds. This means that in this time interval the message is not available/visible for other consumers. Once we process the message we can mark it as processed. If we don't mark the message as processe...
Post a Comment
Read more