How do I link multiple TFS 2012 Build Definitions into a single build definition -
how or can i, create hierarchy of build definitions in tfs 2012?
i have master build script (.cmd) calls multiple child scripts (.cmd).
want migrate tfs build system , maintain hierarchy.
i can't seem figure out if possible using tfs 2012 build system.
here's i'm talking about: masterbuildscript.cmd call componentscript1 call componentscript2 call componentscript3 call ... call packaging routine components
componentscript1.cmd build solution componenta1 build solution componenta2 build solution componenta3 ...
componentscript2.cmd build solution componentb1 build solution componentb2 build solution componentb3 ...
more components...
is there way standard tfs 2012 build definitions? - bruce
there way without doing custom coding. have make minor addition build process template, however. doesn't use code, uses windows workflow foundation.
essentially, need setup tfs team build definitions each .cmd build script have. 1 master build, 1 each component build. real work involved here converting .cmd script tfs build definition.
then, auto queue "child" builds, can edit process template master build definition , add "invokeprocess" activity - lets shell out command line part of build process. can use command line utility tfsbuild.exe kick off "child" builds. http://msdn.microsoft.com/en-us/library/aa337622(v=vs.90).aspx
i've used similar in past have build core set of assemblies. build kicks off of builds have dependencies on assemblies.
Comments
Post a Comment