Team Foundation Server Build Extensions Power Tool December 2011
The Team Foundation Build Extensions provide the ability to execute Ant or Maven builds from Team Foundation Server and publish the results of the build along with any associated JUnit test results back to Team Foundation Server.
We didn't do any testing against Maven 3.X yet for the March 2011 release, but sounds like we should. I would certainly like to see us work well with Maven 3 as soon as possible, just need to figure out what this is going to take. Let me look into this and get back to you.
Actually, it is possible to run Maven 3 builds with TFS 2010. Everything you have to do is, rename the plexus-classworlds-2.4.jar in the boot/ folder to something like classworlds-*.jar. The classworlds file name changed in Maven 3.
Seems that TFS picks up the jar from the boot folder, just like the mvn.bat would do it. Could you confirm this Martin?
The only documentation, that I have seen, on these extensions is in on the description tag. It mentions that the extensions(Ant or Maven) can be made use of in the build definition via MS VS Team Explorer Everywhere. My question is 'How'? Is it through the MSBuild Arguments?
In Team Explorer Everywhere when you create a build definition using the TFS plug-in for Eclipse it will create a build definition that is automatically using the build extensions. Basically is created a TFSBuild.proj file formatted for you with the appropriate import of the .targets file and then a declaration of the Ant or Maven properties necessary to perform the build. If you would like to build the Ant or Maven project without using TEE then let me know and I'll document the manual steps to do this from Visual Studio.
I was asking myself the same thing and we want to do it with Visual Studio 2010. Could you give me some info how to do this manually with Visual Studio? An example how to use it with maven would be great.
Is it TFS Build Extensions the same thing as Teamprise Build Extensions? I am new to this, I am confused. I am in the process to migrate JAVA code from Subversion to TFS and we want to be able to define automatic builds for continuous integration. I am researching to figure out what needs to be done. We have TFS 2008.
Thanks in advance,
The TFS Build Extenions are based on the code in the Teamprise Build Extensions that Microsoft acquired in November 2009. Since that time the TFS Build Extensions have undergone a major re-write for TFS2010 compatibility and also numerous bug fixes and improvements - but they are based on the same codebase. They work with TFS2010, TFS2008 and TFS2005.
Hope that helps,
We use TFS 2010.
There is one build Controller hosted on the machine where we have TFS and several Build Agents located on different machines.
There is a separate Build Agent to be used only for building Java projects and it's located on a separate machine (where we have also Ant installed).
Build Extensions Tool is also installed on that machine.
Now I have created the build Definition and after building it shows error that it can't find the imported project "C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v10.0\BuildExtensions\Microsoft.TeamFoundation.Build.Extensions.Ant.targets" but it's located on the Build Agent machine.
From this seems that it tries to use another Build Agent (default which is located on a different machine).
So is there ability to specify which Build Agent to use in the Build Definition created in TFS Eclipse Plugin?
Or maybe this problem comes from other source?
I'm afraid that to specify the build agent filter today you have to edit the build definition in Visual Studio and set the agent filter property on the build definition. This should then work as expected. We're aware of this as a limitation and wanted to get build definition property editing in the SP1 release of the Eclipse plug-in but we were unable to do so. We continue to try to come up with a better solution for this. Apologies - Martin.
We have TFS 2010.
Now we have to create a separate Build Service to handle JAVA application builds.
So for that we are using ANT.
My question is: What are the specifics for creating Build Definition which will use ANT? (any specific Build Process Template?)?
Can you provide a short step scenario for creating this kind of Build Definition?
I have been trying to create a new build definition to build my java sources from ant. I have an exisiting build.xml and when I try to create a TFSBuild.proj file through Team Explorer Build defintion , I get a Team Explorer error - "Unable to Determine the upgrade process template for the the Team Procject XXXX". I have the Upgrade build Process template living within the version control folder. Why would the new tfsbuild.proj creation wizard not find the upgrade process template and throw up this error?
I am trying to create a Maven 2 build and I keep getting the "Unable to Determine the upgrade process Template error", I have tried a lot of options but the problem persists.
The "Unable to determind the upgrade template" issue is due to the fact that the upgrade template no longer exists for that particular team project. I'd love to understand why that is if you know. What team process template was used to create the project, was the upgrade template deleted by someone? If you want to drop me a line (firstname.lastname@example.org) I can help you restore the upgrade template to the team project.
Will these build extensions be released so as to allow us to use our Unix Build environment for doing maven based builds from a TFS 2010 Build Controller? We would love to see non windows based build agents work with TFS Build Controllers.
These build extensions do not yet allow working with non-windows based build agents. We're aware of the need to do this but don't have anything to announce at this time in regards to that capability. The workaround at this time is to use an alternative build server solution such as CruiseControl, Hudson etc that have TFS integration and work cross platform. There are also commercial alternatives such as OpenMake's Meister product.
We fix the reported bugs in this latest March release as try to do every power tools release. In the future I want to invest in the documentation around this area as well as provide some guidance as to how you would have a build definition that built both Ant or Maven alongside a .NET solution.
We also hope to provide additional build extensions that will be of use to the community. If you have any suggestions for features that you would like to see then please let me know.
does TFS 2010 has 1.1 support. I use vs 2010 with MSbee and target framework 1.1. I added my project to TFS 2010 but i could not build it fine. It is always gives Microsofot.CompactFramework.Build.Tasks.dll could not load error. I could not find any information about this stiuation. Do you have any idea ?
Thanks in advance.