Hi,
We have two scenario's. In both cases we have CI and NB builds.
Sometimes we have also like you a test build for trying out stuff before
merging in the other builds. But as you said most of the times the
managers are standing at our desk when this build goes in red alert J.
If we use this we give it a typical name so everyone can see that it's a
test build (something like TryOutBuildIngoreFails).
But most of the times (I can say 90% of our projects) I use my TFS VPC
for it. In this case I'm the only one who gets the red alerts J. My
TFS VPC has really a lot of handy tools,... installed. Customers don't
allow us sometimes to install them also on their server. So for me this
helps me in my work, before putting the new buildscripts on the real TFS
server.
In my opinion using a TFS VPC for test purposes is the best process.
Sven Cipido
.Net Solution Architect, Agile Consultant, Buildserver Consultant
ORDINA Belgium
Contact Details
B-2627 Schelle (Antwerpen), Boomsesteenweg 28
B-3001 Leuven, Interleuvenlaan 15H
B-3560 Lummen, Bosstraat 52/2
B-9820 Merelbeke, Guldensporenpark 84/I
+32 (0)3 866 00 22
+32 (0)3 866 03 01
+32 (0)496 122 413
@ [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
Blog : http://blog.svencipido.be <http://blog.svencipido.be/>
Blog : http://blog.n-technologies.be <http://blog.n-technologies.be/>
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
www.ordina.be
<https://212.35.120.78/exchweb/bin/redir.asp?URL=http://www.ordina.be/>
Email Disclaimer
The information contained in or with this email, originating from
Ordina, is confidential and intended solely for the addressee. If this
email has been received in error the receiver is kindly asked to contact
the sender via email or telephone. Revelation, reproduction,
distribution and/or forwarding of the information contained to third
parties is not permitted. Ordina is not responsible for the correct and
complete transference of the content of any transmitted email, nor for
the timely reception thereof, nor for the correctness of the content. In
no case is Ordina liable for any damage, in any form, which may arise as
a direct or indirect consequence of acting and/or neglecting and/or
deciding anything based wholly or partly on this email. On all
activities and offers of Ordina, and in all agreements of which they are
directly or indirectly a party, the General Terms and Conditions apply,
even if not included. A copy of these Terms and Conditions will be sent
to you free of charge on request.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Steven Nagy
Sent: donderdag 8 mei 2008 8:37
To: [email protected]
Subject: [OzTFS] Team Build Maintenance Methodology
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
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
<<image001.gif>>
<<image002.png>>
<<image003.png>>
<<image004.png>>
<<image005.png>>
