[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Intelligent commit triggers
From: |
Todd Denniston |
Subject: |
Re: Intelligent commit triggers |
Date: |
Thu, 26 Jul 2007 09:22:42 -0500 |
User-agent: |
Thunderbird 2.0.0.5 (X11/20070716) |
Hans Schwaebli wrote, On 07/26/2007 09:00 AM:
In CruiseControl I can use something like this:
<modificationset quietperiod="1" >
<compound includeTriggerChanges="false">
<triggers>
<filesystem folder="./mod_file.txt" />
</triggers>
<targets>
<cvs
cvsroot=":pserver:address@hidden:/cvs"
/>
</targets>
</compound>
</modificationset>
Our CVS administrator managed to write a trigger which touches a file whenever something is comitted into the CVS repository.
But this does not distinguish into which branch something is checked in.
Since we have two branches, one for active development line and one for release line, and thus two builds, we need a trigger which distinguishes on which branch something is checked in.
If something is checked into the active development line branch, then file A has to be touched, if something is checked into release line, file B has to be touched.
This seems to be very basic needs, but also very in-depth knowledge of CVS and Linux batch scripting needed, which I don't have.
Can someone please tell me how to accomplish this?
You should send these questions directly to the address@hidden list.
My only other suggestion that may be of help is, look at cvs_acls, it may
point you in the right direction.
http://cvs.savannah.nongnu.org/viewvc/ccvs/contrib/cvs_acls.pl?revision=1.6&root=cvs&view=markup
http://cvs.savannah.nongnu.org/viewvc/*checkout*/ccvs/contrib/cvs_acls.html?revision=1.3&root=cvs
--
Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane)
Harnessing the Power of Technology for the Warfighter
- Re: Intelligent commit triggers,
Todd Denniston <=