Re: CruiseControl Not Deploying Changes on a CVS Branch

Chuck Burgess <[email protected]>
Newsgroups gmane.comp.java.cruise-control.user
Message-ID <[email protected]>
On Thu, Sep 10, 2009 at 11:54 AM, Flaisher, Harvey (NIH/NCI) [C] <
[email protected]> wrote:

>  Hi Chuck:
>
>
>
> Thank you.  In config.xml, our modificationset tag defines only the module:
>
>
>
>     <!-- Defines where CruiseControl looks for changes, to decide whether
> to run the build -->
>
>     <modificationset quietperiod="10">
>
>       <cvs cvsroot=":pserver:...." module="hints"/>
>
>     </modificationset>
>
>
>
>     <!-- Configures the actual build loop, how often and which build
> file/target -->
>
>     <schedule interval="20">
>
>       <ant buildfile="build-hints205.xml" uselogger="true"/>
>
>     </schedule>
>
>
>
> The <ant> buildfile contains the CVS task info, with branch:
>
>
>
> <project name="build-hints205"
>
>         default="build"
>
>         basedir="projects/hints205">
>
>     <target name="build">
>
>         <!-- Get the latest from CVS -->
>
>         <cvs command="update -P -d -r BR-2-0-5-1"/>
>
>         <!-- Call the target that does everything -->
>
>         <ant antfile="build.xml" target="deploy"/>
>
>     </target>
>
> </project>
>
>
>
> This used to work fine.  Do you see a problem doing it this way?
>
>
>
> Thanks much.
>
>
>
> Regards,
>
> Harvey
>


Hey Harvey,

The *modificationset->cvs* looks like it's only checking for modifications
on HEAD, since it doesn't look like you're specifying which branch to check
for modifications against.  Since my builds usually keep the CVS sandbox
copy (rather than clean and checkout on every build), I use the *cvs* target
with the *localworkingcopy* attribute.  That points the task to your
checkout copy, which already contains both the CVS repository info *and the
CVS branch (if any)*.  I see you specify the branch in your buildfile's
"build" target, but remember, that doesn't get executed unless *
modificationset* detects some code changes.

Bottom line, I think your *modificationset* is checking for changes only
against HEAD, not against your branch...  hope that helps.
-- 
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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.