From: Tyler <tyl...@cr...> - 2004-07-26 17:04:19
|
On Mon, Jul 26, 2004 at 10:16:20AM -0600, Randy Novick wrote: > I don't specify my checkout command in my CC config file. Rather, I have > a target in my wrapper buildfile that uses ANT's <cvs/> tag to perform > the checkout of my branch. Could it be that I am setting myself up for > conflicts by doing so? Maybe some config can show what I'm doing: > > So here's my modificationset for my 33._branch project: > > <modificationset quietperiod="300"> > <cvs cvsroot=":pserver:rnovick@<ip_addr>:<cvs_dir>" > > localworkingcopy="/opt/cruisecontrol-2.1.5/work/cruise/checkout/3.3_branch/dwe"/> > </modificationset> > > Here's my checkout target from the 3.3_branch project's wrapper buildfile: > > <target name="checkout" > description="Checks out the dwe source tree from CVS" > depends="nuke"> > <cvs cvsroot=":pserver:rnovick@<ip_addr>:<cvs_dir>" > package="dwe" > command="checkout -P -r DWE_3_3_branch dwe" > dest="checkout/3.3_branch"/> > </target> You still need the <tag> attribute, because cc passes that "tag" (really a branch, as you noted) to cvs log to discover modifications. > Anyhoo, I am indeed using 2.1.5. Can anyone shed some further light on > Joris' recollection of the bug in 2.1.5? > If what I want to do just won't work in 2.1.5, I'd like to spare myself > the anguish of making the change and still having things not work > properly when an upgrade to 2.1.6 is a necessity. You either need 2.1.6, or you can apply a patch that fixes the broken "log -N" behavior in 2.1.5 and recompile your cc. Search the archives for posts by me in the last couple months and you should find said patch. tyler > Korver, Aaron wrote: > > >Yes, I think you got it. Maybe this example will help: > ><modificationset quietperiod="10"> > > <cvs cvsroot=":pserver:XXXXXXX" tag="XXXXXXXXXX" > >localworkingcopy="checkout/"/> > ></modificationset> > > > >This says use this tag to check things out. The tag is the name of > >the branch. > > > > > >> -----Original Message----- > >> From: cru...@li... > >> [mailto:cru...@li...]On Behalf Of > >> Randy Novick > >> Sent: Monday, July 26, 2004 10:33 AM > >> To: Cruisecontrol Users > >> Subject: [Cruisecontrol-user] ... multiproject CC with CVS > >> branches ... > >> > >> > >> Hello All, > >> > >> I'm diving headlong into the multiproject configuration and my first > >> attempts are puzzling. I'm using CVS, and my goal is to > >> create a project > >> for each CVS branch. I have a MAIN_TRUNK project, and one for > >> 3.3_branch. Funny thing is that when the 3.3_branch project runs, the > >> report shows the changes that were made on the MAIN_TRUNK. > >> Looking into > >> the (now nicely reformatted -- thanks, Joe!) documentation at > >> CruiseControl Home, I see that the <cvs/> element has a tag > >> attribute, > >> though what the attribute actually does is not very clear. > >> > >> "Set the CVS tag?" This sounds like the application of a tag, rather > >> than specifying the tag to use for modification check. > >> > >> My assumption, given the latter interpretation of the tag > >> attribute, is > >> that I need to specify my CVS branch tag in the <cvs/> > >> element that I'm > >> using in my 3.3_branch project. Am I on the right track? I didn't see > >> anyplace else where I could refer to the branch tag. > >> > >> If anyone has had any experience with setting up multiple CC > >> projects to > >> run builds of CVS branches, I'd appreciate any advice on the matter. > >> > >> Many thanks, > >> -- R > >> > >> > >> > >> > >> ------------------------------------------------------- > >> This SF.Net email is sponsored by BEA Weblogic Workshop > >> FREE Java Enterprise J2EE developer tools! > >> Get your free copy of BEA WebLogic Workshop 8.1 today. > >> http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click > ><http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click> > >> _______________________________________________ > >> Cruisecontrol-user mailing list > >> Cru...@li... > >> https://lists.sourceforge.net/lists/listinfo/cruisecontrol-user > >> > > |