TFS multiple builds and build numbering
There were two problems in making a new automated build.
1. TFS requires a new build agent for every team project
That means either installing 2 build services on Periyar or having a new build machine
(Are we getting any value add out of having a separate team project for every branch?)
2. The same folder cannot be used as the workspace for more than one source control folder
C:\XYZ can be used only for any one build
The workarounds I did were
1. I am defining both the builds in the XYZProduct2 team project (I can point to any source control folder anyway)
2. There are now 3 virtual folders pointing to the same physical folder
linkd C:\XYZ D:\Projects\Builds\Sources
linkd D:\Projects\Builds\XYZProduct2 D:\Projects\Builds\Sources
linkd D:\Projects\Builds\XYZProduct5.1.0.10 D:\Projects\Builds\Sources
For every new build, we can make a new virtual folder and point it to D:\Projects\Builds\Sources
C:\XYZ will always point to this folder anyway.
So all builds happen in one folder with the same agent.
TFS just thinks they are different folders.
I have already checked both builds with the following params and they were working fine
\\periyar\LiveComm\Builds\ (since Narmada was down)
/p:DB=No
For the build numbering, I have now made UpdateAssociatedWorkItems an optional parameter and set the default to false.
So work items will not get updated with the build number any more.
We could either do this manually after a build
Or
Go for one of the solutions below.
Will update TFS and discuss more with you on this.
http://www.tfsbuild.com/Increment%20Build%20Numbers%20(major,%20minor,%20build,%20etc).ashx
Incrementing the build number, and versioning the assemblies with a 3rd party API
http://msdn.microsoft.com/en-us/library/aa395241(VS.80).aspx
Customize Team Foundation Build by creating your own custom tasks that run during a build
1. TFS requires a new build agent for every team project
That means either installing 2 build services on Periyar or having a new build machine
(Are we getting any value add out of having a separate team project for every branch?)
2. The same folder cannot be used as the workspace for more than one source control folder
C:\XYZ can be used only for any one build
The workarounds I did were
1. I am defining both the builds in the XYZProduct2 team project (I can point to any source control folder anyway)
2. There are now 3 virtual folders pointing to the same physical folder
linkd C:\XYZ D:\Projects\Builds\Sources
linkd D:\Projects\Builds\XYZProduct2 D:\Projects\Builds\Sources
linkd D:\Projects\Builds\XYZProduct5.1.0.10 D:\Projects\Builds\Sources
For every new build, we can make a new virtual folder and point it to D:\Projects\Builds\Sources
C:\XYZ will always point to this folder anyway.
So all builds happen in one folder with the same agent.
TFS just thinks they are different folders.
I have already checked both builds with the following params and they were working fine
\\periyar\LiveComm\Builds\ (since Narmada was down)
/p:DB=No
For the build numbering, I have now made UpdateAssociatedWorkItems an optional parameter and set the default to false.
So work items will not get updated with the build number any more.
We could either do this manually after a build
Or
Go for one of the solutions below.
Will update TFS and discuss more with you on this.
http://www.tfsbuild.com/Increment%20Build%20Numbers%20(major,%20minor,%20build,%20etc).ashx
Incrementing the build number, and versioning the assemblies with a 3rd party API
http://msdn.microsoft.com/en-us/library/aa395241(VS.80).aspx
Customize Team Foundation Build by creating your own custom tasks that run during a build
Comments
Post a Comment