Hi all, So I want to put out the question around how people do team build developement. We have a big project, we have 3 different CI builds and a Main build. We also have a test build that we use to 'try stuff' and come up with solutions before merging into the main build. We were about to do the same with the CI builds but thought "there must be a better way".
I find that for some things I can use MSBuild directly from the command line. But this doesn't let me deal with team build specific issues (overriding core targets, 'SolutionToBuild' item group, etc). And the approach with using a test build works, but it has high visibility. In other words, when it fails, everyone can see that it failed. Red lights cause alarm, project managers want to know how it will affect the nightly build, etc. So I'm just curious... what is a more accepted process? Should we be doing all build development in a TFS VPC? Or in the same TFS but different team project? What is a common practise? What's working for you guys in other projects? Appreciate all feedback. Cheers, Steven ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________ OzTFS.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. View the web archives at http://www.mail-archive.com/[email protected]/ Powered by mailenable.com, supported by www.readify.net
