[oclug] complicated CVS setup
Gilles J. Seguin
segg at infonet.ca
Thu Apr 26 15:40:30 EDT 2001
"David F. Skoll" wrote:
> On Wed, 25 Apr 2001, Bart Trojanowski wrote:
> > Ideally I want the user to be forced to update, recompile, test, then
> > commit. However I know I cannot force them to do the compile/test steps
> Why not? Have your commitinfo script
saved commit stuffs to a working directory, to allow
> run a compilation and regression-test.
follow by email, with result of last build
and every night, a cron for rebuilding every thing
> This will probably discourage people from committing very often,
> however. :-)
> > I will set a threshold in an
> > /etc/cvs-uptodate.conf file and if the user has not updated a file he is
> > attempting to commit in more than specified days I will produce a warning.
> CVS will not let you commit without updating, so I don't see the purpose
> of this.
More information about the OCLUG