info-cvs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Fwd: Intelligent CVS trigger?


From: Hans Schwaebli
Subject: Fwd: Intelligent CVS trigger?
Date: Wed, 21 Mar 2007 07:54:03 -0700 (PDT)

What about this?


Hans Schwaebli <address@hidden> wrote:
Date: Wed, 21 Mar 2007 02:10:34 -0700 (PDT)
From: Hans Schwaebli <address@hidden>
To: address@hidden
Subject: Intelligent CVS trigger?

For our daily and nightly builds it would be good to use CVS trigger which touches a file after a commit. Then only this file would be checked to determine if a build is needed.
 
But this trigger would need to be intelligent. It must only touch the file if files with certain extensions have been committed. For example a new build is not necessary if someone checks in a Word document. Furthermore we need two such touched files, one for the HEAD and one for the release line branch. If someone checks into the release line branch, the trigger must not touch the file which represents modifications on the HEAD. It must instead only touch the file which represents modifications on the release line branch.
 
Please consider that I am a windows guy and that our CVS server is a Linux machine. So it would be nice if you can tell me a example script or something which makes it easy to implement this. Thank you very much.
 
We have to do the whole thing because CVS needs a lot of time to determine whether modifications occured. It takes at least 15 Minutes. By just checking one file for its touch date, this can be speeded very much.

Get your own web address.
Have a HUGE year through Yahoo! Small Business._______________________________________________
info-cvs mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/info-cvs


TV dinner still cooling?
Check out "Tonight's Picks" on Yahoo! TV.
_______________________________________________
info-cvs mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/info-cvs

reply via email to

[Prev in Thread] Current Thread [Next in Thread]