Re: CruiseControl Not Deploying Changes on a CVS Branch

On Fri, Sep 11, 2009 at 1:20 PM, Flaisher, Harvey (NIH/NCI) [C] <
[email protected]> wrote:

>  Hi Chuck:
>
>
>
> You were right, addition of the tag attrib worked:
>
>
>
>     <modificationset quietperiod="10">
>
>       <cvs cvsroot=":pserver:..." tag="BR-2-0-5-1" module="hints"/>
>
>     </modificationset>
>
>
>
> I am just perplexed as to how it was working all this time without that.
>
>
>
> Thanks very much, you saved us a lot of time.
>
>
>
>
>
> Regards,
>
> Harvey
>


One scenario that I can see for it originally working is that there just
happened to be enough commits occurring against HEAD (i.e. the trigger to
run builds) to keep you thinking that it was commits against the first
branch that were triggering the builds.  Since the builds themselves were
properly updating against the branch (based on your build target), the
builds would look perfect.  Had there not been much commit activity against
HEAD, while having lots of activity against the branch, you would have
certainly noticed something wrong.

I'm guessing that the addition of the new branch prompted a closer watching
of its build process, thus revealing that commits on it were not triggering
its builds.  I think that if your original branch's build hasn't been
corrected, and you stopped all HEAD commits while doing some branch commits,
you'd see the same lack of builds being triggered by CC.

Glad you got it solved though, Harvey... full speed ahead ;-)
-- 
CRB

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july

_______________________________________________
Cruisecontrol-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/cruisecontrol-user