Execute custom code during Tfs build
At this point I explained how to setup a build, and how to fully customize it editing the msbuild file to execute some tasks, like open an issue when one or more test fail.
Another interesting stuff to explain is how to execute custom code during the build, to demonstrate this concept I’ll show how to tweet a warning message when test phase fails. To execute custom code you simply need to create a custom msbuild task that does everything you want, then you simply need to call this custom task in the build script. The first step is creating the task.
|
|
As you can see, creating a custom task is really simple, you should inherit from the Task base class and override the Execute() method. In this example everything is done in the TwitterService class that I took from this post. To pass parameters to this task you can simply create public properties in the task class, and use the [Required] attribute to specify that the caller absolutely needs to specify these properties to use the task.
Now you only need to compile this class into a dll, and make it avaliable to the build process. This is probably the most interesting part, because the build engine must be able to locate this dll in order to execute your custom action. Another requirement I want, is that you must be able to use your custom task without the need to physically go to tfs server and copy the dll into some directory. This because you must be able to fully configure the build with the same set of permission you have in tfs. I do not want to ask someone Hey copy this dll into the tfs server, I simply want to configure everything in visual studio.
This is a well known problem for everyone that works with Continuous integration machines, and the solution I like is inserting everything is needed for the build in a specific folder into the source control system of the project.
As you can see I created a folder called BuildTools, inside it another folder called MsBuildCustomTasks and inside the compiled dll with my actino. Now I’m sure that the dll with my custom task is included into the source control system, and I can refer to it inside the TFSBuild.proj build file.
|
|
to import the custom task you simply need to specify the task name and the assemblyFile in a <UsingTask> directive, as you can see the path of the dll is..\sources\xxx where xxx is the path of the dll relative to the root of the source control system. Now if you do a check-in the next build will comprehend your custom task. This technique is useful, because you can be sure that each build always do a Get Latest to build the latest version of the source, thus getting also every tool it need to do the build.
Now you can use this task wherever you want:
|
|
As for the previous post, I’m asking to tweet a message to my twitter account when test phase fails during the build, I made a test fails, commit everything and after integration machine finished to build I can see this in my twitterDesk
WOW :D you can have your CI machine tweet whenever you want with less than 20 lines of code. You can now create a dedicated twitter account for every project you have, and you can follow status of the build in every device that supports twitter :D.
Alk.
Tags: Team Foundation Server