How to force the developers to compile before protect the
code into SourceSafe?

Hi,

 In my development team it is very common to someone protecting something that
does not work. The solution should be (if that person does not understand how
easy is to compile and check for errors before compiling) is to FORCE it. It is
t'hat possible?

I know whith team system this feature is enabled, but we do not have it for the
moment.

 

Thanks

Successfull build on a developer machine does not necessarily means build will
not be broken on other machines. For example, if I add a new file but forget to
check it in, the build will succeed on my box but will fail on another dev
machine. Rolling build may use the same machine as nightly/daily build - it does
require a separate machine though. Here is my team process :-), all steps are
mandatory.

1. Code review from another developer familiar with the feature area. Two code
reviews if change is significant or we are close to the release.

2. Build on dev machine, unit tests are successfull.

3. TS to a checkin machine (dedicated high performance box).

4. Submit changes.

5. Run automated checkin process on the checkin machine: another build, both
retail and debug, automated tests again. ~3 hours.

6. If #5 successfull, machine sends checkin e-mail and updates safe sync label
(devs to do not sync to the latest hot sources, only to safe labels). Otherwise
dev must investigate ASAP.

In addition: nightly builds including setup, nightly QA automation runs
(multiple machines, several hours, 800+ tests), weekly QA automation runs
(thousands of tests, takes 2 days to complete + failure analysis)

This is all for the private team branch. Additional testing is required before
integration into VS Main branch (integration takes ~3 days via automated
system). There are additional steps when product is close to release (such as
testing and sign off is required from QA for every change submitted and approval
from division ship room).

Hi, That seems to be a very strict way of work, that should get you in very good
quality results.

 We want to move there. I think MS Team System helps on that, I don't know if
you use this, another or a custom software for the job, but I was looking for
something more simple at the moment.

 Thanks anyway

Typically #1, #2 and rolling build covers most of the issues. How long does it
take you to build your solution?

Hi,

 Not much. You are right, steps 1 and 2 are ok. The problem is with the junior
developers, their behaibour is... more... difficult (as is expected)