We've got TFS 2010 set up with continuous integration - Every code checkin results in a build and a publish of the website to a dev server.
We've now got a second project that is referenced by the first. The second is a stand-al开发者_如何学Pythonone application with a few assemblies. Our website points at one of those assemblies.
I've managed to edit our CI build definition so that Project2
gets built before Project1
. Project1
builds correctly, and finds the references to Project2
.
What I'd like it to do is also build the stand-alone app for Project2
at the same time (it isn't visible anywhere in the output from the Project1
CI build).
Can/should I do this all using a single build definition? Do I need to create multiple build definitions with the same triggers?
You can add the second project's source under the workspace section of your build definition. After that you should be able to select the sln or xxproj for the stand-alone app.
My generally feeling is that having build dependencies across team projects is something of a smell. I would often elect to put them in the same team project since they seem to depend tightly on one another or make Project1 an opt-in dependency of Project2, but pulling the build output of successful Project1 builds that can be accommodated into Project2.
Just a thought.
精彩评论