RTC support for NANT
Apologies is this has been asked before but I understand that RTC builds support ANT but are there any plans to support NANT? I've read some details about the extra ANT tasks provided with RTC to notify RTC of the build progress and make sure the build area has accepted all change sets etc which are very useful but am concerned that I may not have equivilent functionality with my NANT build scripts.
We mainly use Visual Studio developing C# applications and currently use CruiseControl for continuous integration but calling NANT build scripts to perform the main build. We use a range of VS versions from 2..5 right up to 2010 and .NET 2 up to .NET 4
For those people who have a similar setup and are successfully using RTC build engines etc., I would be very interested to know what scripting tools you use to manage the builds themselves.
Thanks in advance
David
We mainly use Visual Studio developing C# applications and currently use CruiseControl for continuous integration but calling NANT build scripts to perform the main build. We use a range of VS versions from 2..5 right up to 2010 and .NET 2 up to .NET 4
For those people who have a similar setup and are successfully using RTC build engines etc., I would be very interested to know what scripting tools you use to manage the builds themselves.
Thanks in advance
David
8 answers
Hi David,
I've integrated a .bat file based build system with Team Concert not because team concert supports .bat files, but because it's rather simple to call out to Ant and use the build toolkit we provide from any language.
I outlined a quick overview of the .bat file calls in
http://jazz.net/blog/index.php/2008/11/14/integrating-visual-studio-builds-with-team-concert/
You could do something similar form NANT.
:StartActivity
java -cp %CLASSPATH% %ANT_LAUNCHER% -f %DEST_DIR_PATH%\RTC.NET Client\jazzBuildTasks.xml -lib %JAZZ_TOOLKIT% -DuserId=%BUILD_USER_ID% -DpasswordFile=%JBE_PASS_FILE% -DrepositoryAddress=%REPOSITORY_URL% -DbuildResultUUID=%BUILD_UUID% -DactivityLabel=%1 startActivity
GOTO :EOF
:PublishFile
java -cp %CLASSPATH% %ANT_LAUNCHER% -f %DEST_DIR_PATH%\RTC.NET Client\jazzBuildTasks.xml -lib %JAZZ_TOOLKIT% -DuserId=%BUILD_USER_ID% -DpasswordFile=%JBE_PASS_FILE% -DrepositoryAddress=%REPOSITORY_URL% -DbuildResultUUID=%BUILD_UUID% -Dfile=%1 -Dlabel=%2 -Dtype=%3 publishFile
GOTO :EOF
Jean-Michel
I've integrated a .bat file based build system with Team Concert not because team concert supports .bat files, but because it's rather simple to call out to Ant and use the build toolkit we provide from any language.
I outlined a quick overview of the .bat file calls in
http://jazz.net/blog/index.php/2008/11/14/integrating-visual-studio-builds-with-team-concert/
You could do something similar form NANT.
:StartActivity
java -cp %CLASSPATH% %ANT_LAUNCHER% -f %DEST_DIR_PATH%\RTC.NET Client\jazzBuildTasks.xml -lib %JAZZ_TOOLKIT% -DuserId=%BUILD_USER_ID% -DpasswordFile=%JBE_PASS_FILE% -DrepositoryAddress=%REPOSITORY_URL% -DbuildResultUUID=%BUILD_UUID% -DactivityLabel=%1 startActivity
GOTO :EOF
:PublishFile
java -cp %CLASSPATH% %ANT_LAUNCHER% -f %DEST_DIR_PATH%\RTC.NET Client\jazzBuildTasks.xml -lib %JAZZ_TOOLKIT% -DuserId=%BUILD_USER_ID% -DpasswordFile=%JBE_PASS_FILE% -DrepositoryAddress=%REPOSITORY_URL% -DbuildResultUUID=%BUILD_UUID% -Dfile=%1 -Dlabel=%2 -Dtype=%3 publishFile
GOTO :EOF
Jean-Michel
Hi David,
We have something planned around 'gated checkin', not sure if it will make 3.0, but we could get something simple in place. We have all the pieces with repo workspaces and personal builds, etc...
See 63209: block delivery of a change when a particular build (e.g. a personal build) is not green (gated deliver)
Jean-Michel
We have something planned around 'gated checkin', not sure if it will make 3.0, but we could get something simple in place. We have all the pieces with repo workspaces and personal builds, etc...
See 63209: block delivery of a change when a particular build (e.g. a personal build) is not green (gated deliver)
Jean-Michel
Hi David,
We have something planned around 'gated checkin', not sure if it will make 3.0, but we could get something simple in place. We have all the pieces with repo workspaces and personal builds, etc...
See 63209: block delivery of a change when a particular build (e.g. a personal build) is not green (gated deliver)
Jean-Michel
We have something planned around 'gated checkin', not sure if it will make 3.0, but we could get something simple in place. We have all the pieces with repo workspaces and personal builds, etc...
See 63209: block delivery of a change when a particular build (e.g. a personal build) is not green (gated deliver)
Jean-Michel
Below the Build Log field shown in the screen shot, there are the following fields:
- Additional arguments
- Properties file
- Working directory
So the args for Debug or Release could be added in the Additional arguments field.
If these are common choices though, maybe they should be given first class support in the UI.
- Additional arguments
- Properties file
- Working directory
So the args for Debug or Release could be added in the Additional arguments field.
If these are common choices though, maybe they should be given first class support in the UI.
Below the Build Log field shown in the screen shot, there are the following fields:
- Additional arguments
- Properties file
- Working directory
So the args for Debug or Release could be added in the Additional arguments field.
If these are common choices though, maybe they should be given first class support in the UI.
The build configurations are not predefined(even Debug/Release can be deleted from a solution), they can be custom defined by a user for a particular solution. In the "Microsoft Build" page their is a separate field "Build Configuration" where the user can specify the configuration to build.