Releasing multiple projects for one solution
I have a Visual Studio solution with one SSRS project, two SSIS projects, one SSAS project, and one SQL Server project. I am using TFS2013 Update 4.
I would like to deploy this solution using TFS release control in two environments. The first environment should be "populated" after the developer is registered and in the second environment projects should only be deployed the next night (during the day the environment is used by testers and a new deployment may affect their data).
Can this be done with TFS Release Manager 2013.4?
Update 1:
The single gated registration build is taking too long and so at this point I have gated locks on each project to keep developer latency to a minimum.
Update 2:
Current setup with five gated registration lines that build and deploy each project to the first environment and one nightly build that builds and deploys the entire solution to the second environment.
source to share
Add an optional "collector" assembly that you automatically enqueue from others whose purpose is to collect artifacts and link to the release manager.
In other words, let's say you have five CI assemblies, one for each project named CI1-CI5. In each CI post-test script, you run a similar command
TFSBuild start /collection:%TF_BUILD_COLLECTIONURI% /buildDefinition:Collector /queue /msBuildArguments:CIDrop=%TF_BUILD_DROPLOCATION%
for the build queue Collector
. This latter collects artifacts from the parent build, and the latter knows the good artifacts of the remaining CI builds and copies them to its location.
You can now use the Release Manager as usual in this Collector
build.
source to share