Hi,

So there is now an intense amount of coding going on with HPS Java, which is good to see.

However, it seems the trunk builds are being broken a lot lately by various checkins to the SVN, so here are some tips for not breaking the build for everyone else.

1) Using 'svn status' in your IDE, make sure that you have added any new files on which the code now depends (usually done with 'svn add' from the command line).

2) Always build your local copy of the entire trunk which you use for development before committing changes.  This makes sure that a change you make to one module doesn't break the compilation of another.

3) Have a separate, clean copy of the trunk on which you ONLY do 'svn up' to get changes from the server.  After you make a checkin, then update this "read only" copy of the trunk, and build it from scratch.

4) Monitor the continuous integration system to see if your changes cause a build to fail.

http://srs.slac.stanford.edu/hudson/view/HPS/job/hps-modules/

Okay, it is down at the moment, but usually a build will fire off within ~15 minutes of a change occurring.  

Should the build be broken then check the end of the console output for that build to see what happened, e.g.

http://srs.slac.stanford.edu/hudson/view/HPS/job/hps-modules/627/console

5) If you make changes to lcsim (rather than HPS Java) you MUST obviously commit this code first before HPS Java can use it.  (In fact, sometimes the build will break even if you commit the lcsim code, as the snapshot doesn't get deployed in time, but this is only solved by committing lcsim changes first and then waiting for the lcsim build to successfully deploy the snapshot.)

6) Periodically run from your clean trunk copy with all the tests enabled to see that they all pass.

7) If you are going to be doing a lot of potentially breaking changes then make a branch of the trunk to work on:

svn cp svn://svn.freehep.org/hps/java/trunk svn://svn.freehep.org/hps/java/branches/hps-java_my-branch-name

I know some of this might seem like overkill, but especially causing compilation failures can actually prevent others from doing their work, so please be conscientious about how you are committing code to the trunk.

Thanks.

--Jeremy

########################################################################
Use REPLY-ALL to reply to list

To unsubscribe from the HPS-SOFTWARE list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=HPS-SOFTWARE&A=1