From jeremy.lightsmith at gmail.com Fri Aug 1 14:20:36 2008 From: jeremy.lightsmith at gmail.com (Jeremy Lightsmith) Date: Fri, 1 Aug 2008 11:20:36 -0700 Subject: [Cruisecontrolrb-users] CruiseControl.rb is moving to github! Message-ID: <648eacf20808011120qc0f2a92x698e5afcfd23d8ed@mail.gmail.com> In the interest of supporting community participation, easy forking of our codebase and accepting of changes, We're moving to github! check it out - *http://github.com/thoughtworks/cruisecontrol.rb* What does this mean to you? If you generally get new releases of cruise from rubyforge download's page, it doesn't mean anything. We will continue to put all releases on rubyforge. If you generally use pre-release versions of cruise, you'll have to start getting cruise from *http://github.com/thoughtworks/cruisecontrol.rb* If you have changed or are planning on making changes or playing around with your own version of cruise, you should fork off of this version. Github makes this really easy, and when you want to tell us about the cool things you've done, just send us a pull request! Happy coding, Jeremy -------------- next part -------------- An HTML attachment was scrubbed... URL: From matt at mattwynne.net Fri Aug 8 07:08:24 2008 From: matt at mattwynne.net (Matt Wynne) Date: Fri, 8 Aug 2008 12:08:24 +0100 Subject: [Cruisecontrolrb-users] Jabber Notification Message-ID: <9FED035D-C68D-43BE-9EDC-C941FA8725EC@mattwynne.net> Hi all, Some of my team are using ubuntu for their desktop (i.e. no cctray support), and email notification just ain't quick enough for me, so I need to set up our ccrb to support jabber notification, I guess. I read in the documentation (http://cruisecontrolrb.thoughtworks.com/ documentation/getting_notified) that there's a jabber plug but I can't see one in /lib/builder_plugins Where should I be looking? For bonus points a pointer to a blog post explaining how to set it up would be tremendous. cheers, Matt -------------- next part -------------- An HTML attachment was scrubbed... URL: From matt at mattwynne.net Fri Aug 8 07:01:34 2008 From: matt at mattwynne.net (Matt Wynne) Date: Fri, 8 Aug 2008 12:01:34 +0100 Subject: [Cruisecontrolrb-users] Which Version for git support? Message-ID: <62485703-DF65-4F58-8E5E-4A341A268B4D@mattwynne.net> Hi Folks, I've recently moved from a .NET to a rails shop and am helping them set up CI for their tests. CruiseControl.rb looks like exactly what we need, and as a bonus it's a great little app for me to root around in to see how grown-up rails apps should be written (I hope!) One major thing that drew us to ccrb is git support. I asked on the git IRC channel and most people seemed to be using ccrb. I'm a little confused about which version to use though! * The 'official' thoughtworks website http:// cruisecontrolrb.thoughtworks.com/ points to rubyforge, and claims only SVN support. I guess that's because the versions that support git are only experimental at the moment? * There's a branch on github here: http://github.com/benburkert/ cruisecontrolrb/tree/master which I've got working with our git repo. yay! * But then I saw a post from Jeremy Lightsmith very recently on this list (http://rubyforge.org/pipermail/cruisecontrolrb-users/2008- August/000560.html) pointing to the new github branch: http:// github.com/thoughtworks/cruisecontrol.rb So what's the git support like in the new thoughtworks github repo? Should I move over to that? Also, I spotted an issues list on lighthouse (http:// cruisecontrolrb.lighthouseapp.com/projects/9150-cruise-control-rb/ overview), but the official page points to jira for issues. I just found this blog post (http://work.onemanswalk.com/2008/4/23/cruise- control-rb-is-moving-to-lighthouse) so I'm guessing lighthouse is now the one. Might be worth updating the website a little. Great work so far, I look forward to contributing some additions when I get the hang of this ruby lark! cheers, Matt -------------- next part -------------- An HTML attachment was scrubbed... URL: From thewoolleyman at gmail.com Fri Aug 8 07:55:40 2008 From: thewoolleyman at gmail.com (Chad Woolley) Date: Fri, 8 Aug 2008 04:55:40 -0700 Subject: [Cruisecontrolrb-users] Which Version for git support? In-Reply-To: <62485703-DF65-4F58-8E5E-4A341A268B4D@mattwynne.net> References: <62485703-DF65-4F58-8E5E-4A341A268B4D@mattwynne.net> Message-ID: On Fri, Aug 8, 2008 at 4:01 AM, Matt Wynne wrote: > * There's a branch on github > here: http://github.com/benburkert/cruisecontrolrb/tree/master which I've > got working with our git repo. yay! > * But then I saw a post from Jeremy Lightsmith very recently on this list > (http://rubyforge.org/pipermail/cruisecontrolrb-users/2008-August/000560.html) > pointing to the new github > branch: http://github.com/thoughtworks/cruisecontrol.rb I'll tell you what I can. I think that benburkert's should be changed to a branch off the new "official" one, but not sure if that is possible/hard on GitHub. From what I've heard, should be possible if all the branches are deleted? > So what's the git support like in the new thoughtworks github repo? Should I > move over to that? I've found some bugs which I reported on Lighthouse (and tagged with git), and referenced in a recent thread on this list. I think benburkert's may be more stable, but it uses Grit, which has native dependencies. This has been discussed on a separate thread as well. Not sure of the latest status on everything, no updates on those threads... -- Chad From matt at mattwynne.net Fri Aug 8 08:42:33 2008 From: matt at mattwynne.net (Matt Wynne) Date: Fri, 8 Aug 2008 13:42:33 +0100 Subject: [Cruisecontrolrb-users] Which Version for git support? In-Reply-To: References: <62485703-DF65-4F58-8E5E-4A341A268B4D@mattwynne.net> Message-ID: <811800CA-6C74-4E86-BAC1-60D44FFE853E@mattwynne.net> Thanks Chad. I guess I'll stick with benburkert's version for the time being then, and watch here for updates. cheers, Matt On 8 Aug 2008, at 12:55, Chad Woolley wrote: > On Fri, Aug 8, 2008 at 4:01 AM, Matt Wynne wrote: >> * There's a branch on github >> here: http://github.com/benburkert/cruisecontrolrb/tree/master >> which I've >> got working with our git repo. yay! >> * But then I saw a post from Jeremy Lightsmith very recently on >> this list >> (http://rubyforge.org/pipermail/cruisecontrolrb-users/2008-August/ >> 000560.html) >> pointing to the new github >> branch: http://github.com/thoughtworks/cruisecontrol.rb > > I'll tell you what I can. > > I think that benburkert's should be changed to a branch off the new > "official" one, but not sure if that is possible/hard on GitHub. From > what I've heard, should be possible if all the branches are deleted? > >> So what's the git support like in the new thoughtworks github >> repo? Should I >> move over to that? > > I've found some bugs which I reported on Lighthouse (and tagged with > git), and referenced in a recent thread on this list. I think > benburkert's may be more stable, but it uses Grit, which has native > dependencies. This has been discussed on a separate thread as well. > Not sure of the latest status on everything, no updates on those > threads... > > -- Chad > _______________________________________________ > Cruisecontrolrb-users mailing list > Cruisecontrolrb-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users From elmer.rivera at gmail.com Fri Aug 8 09:31:54 2008 From: elmer.rivera at gmail.com (Elmer Rivera) Date: Fri, 8 Aug 2008 21:31:54 +0800 Subject: [Cruisecontrolrb-users] Jabber Notification In-Reply-To: <9FED035D-C68D-43BE-9EDC-C941FA8725EC@mattwynne.net> References: <9FED035D-C68D-43BE-9EDC-C941FA8725EC@mattwynne.net> Message-ID: <43c190410808080631r26590468i595dfee58cd9de54@mail.gmail.com> i belive the 1.2 release contains the available plugin jabber notifier. if you have the installed the 1.3, just copy the lib to your builder plugins. hth On Fri, Aug 8, 2008 at 7:08 PM, Matt Wynne wrote: > Hi all, > Some of my team are using ubuntu for their desktop (i.e. no cctray support), > and email notification just ain't quick enough for me, so I need to set up > our ccrb to support jabber notification, I guess. > I read in the documentation > (http://cruisecontrolrb.thoughtworks.com/documentation/getting_notified) > that there's a jabber plug but I can't see one in /lib/builder_plugins > Where should I be looking? For bonus points a pointer to a blog post > explaining how to set it up would be tremendous. > > cheers, > Matt > > _______________________________________________ > Cruisecontrolrb-users mailing list > Cruisecontrolrb-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users > > From stephendanderson at charter.net Fri Aug 8 12:24:06 2008 From: stephendanderson at charter.net (Stephen Anderson) Date: Fri, 8 Aug 2008 09:24:06 -0700 (PDT) Subject: [Cruisecontrolrb-users] Old Revision Detected? In-Reply-To: <18861599.post@talk.nabble.com> References: <18861599.post@talk.nabble.com> Message-ID: <18894993.post@talk.nabble.com> Stephen Anderson wrote: > > The behavior I'm seeing is that CC.rb always restarts a new build, no > matter what. > > The cruisecontrol.rb/log/myproject_builder.log file shows this: > > [info] [2008-08-06 18:15:59] Build 939.1 FAILED > [info] [2008-08-06 18:16:01] New revision 937 detected > [info] [2008-08-06 18:16:03] Build 939.2 started > > Where should I look next to figure out how to fix this? > > Thanks! > -Steve- > I've found the cause of my problem. svn was not able to actually run svn update because a filename in the svn repository with a non-UTF-8 character. svn's failure was apparently confusing CC.rb. When I removed the offending filename from the svn repository, CC.rb's behavior corrected itself. Thanks! -Steve- -- View this message in context: http://www.nabble.com/Old-Revision-Detected--tp18861599p18894993.html Sent from the CruiseControl.rb - Users mailing list archive at Nabble.com. From averkhov at thoughtworks.com Fri Aug 8 12:56:47 2008 From: averkhov at thoughtworks.com (Alexey Verkhovsky) Date: Fri, 8 Aug 2008 11:56:47 -0500 Subject: [Cruisecontrolrb-users] Old Revision Detected? In-Reply-To: <18894993.post@talk.nabble.com> Message-ID: cruisecontrolrb-users-bounces at rubyforge.org wrote on 08/08/2008 10:24:06 AM: > > [info] [2008-08-06 18:15:59] Build 939.1 FAILED > > [info] [2008-08-06 18:16:01] New revision 937 detected > > [info] [2008-08-06 18:16:03] Build 939.2 started > I've found the cause of my problem. svn was not able to actually run svn > update because a filename in the svn repository with a non-UTF-8 character. > svn's failure was apparently confusing CC.rb. This surely sounds like a CC.rb bug. Can you send me the output of "svn up" when that file was in the repository? -- Alex -------------- next part -------------- An HTML attachment was scrubbed... URL: From thewoolleyman at gmail.com Sun Aug 10 03:23:45 2008 From: thewoolleyman at gmail.com (Chad Woolley) Date: Sun, 10 Aug 2008 00:23:45 -0700 Subject: [Cruisecontrolrb-users] Daemon Cleanup Pull Request Message-ID: OK, trying out the new github thing. Just sent Thoughtworks a pull request for a cleanup of the new daemon code. Please accept using this procedure: http://github.com/guides/pull-requests Thanks! -- Chad From matt at mattwynne.net Tue Aug 12 04:24:17 2008 From: matt at mattwynne.net (Matt Wynne) Date: Tue, 12 Aug 2008 09:24:17 +0100 Subject: [Cruisecontrolrb-users] The CruiseControl server does not provide web URLs for projects Message-ID: <01407218-FE71-41AF-AFF8-0CB278DF24A0@mattwynne.net> Hi folks, We successfully set up our ccrb app, running on a server in-house. As a first pass, I was originally running it through a terminal connected to the server via ssh, where I'd just navigated to the app's folder then run 'cruise start'. At that time, I could connect fine to the CCTray service. We've subsequently 'productionized' it a bit, by setting up a builder account on the server and an /etc/init.d script to start / stop mongrel. I'm now finding that the CCTray service doesn't work. The web site's there OK, but when I try to access the existing CCTray project (actually I'm using the OS-X variant, CCMenu) I get the above error. I can browse the list of projects on the server OK, and add a new one, but the status is just grey. The only difference I can see is that we're just using a straight-up call to mongrel_rails to start the service, rather than using 'cruise start'. Could that be the problem? I can't see anything obvious in the source... cheers, Matt -------------- next part -------------- An HTML attachment was scrubbed... URL: From matt at mattwynne.net Tue Aug 12 05:34:21 2008 From: matt at mattwynne.net (Matt Wynne) Date: Tue, 12 Aug 2008 10:34:21 +0100 Subject: [Cruisecontrolrb-users] The CruiseControl server does not provide web URLs for projects In-Reply-To: <01407218-FE71-41AF-AFF8-0CB278DF24A0@mattwynne.net> References: <01407218-FE71-41AF-AFF8-0CB278DF24A0@mattwynne.net> Message-ID: Folks - sorry: totally false alarm. I restarted CCMenu and it works. I feel like a proper chump! cheers, Matt On 12 Aug 2008, at 09:24, Matt Wynne wrote: > Hi folks, > > We successfully set up our ccrb app, running on a server in-house. > As a first pass, I was originally running it through a terminal > connected to the server via ssh, where I'd just navigated to the > app's folder then run 'cruise start'. > > At that time, I could connect fine to the CCTray service. > > We've subsequently 'productionized' it a bit, by setting up a > builder account on the server and an /etc/init.d script to start / > stop mongrel. > > I'm now finding that the CCTray service doesn't work. The web > site's there OK, but when I try to access the existing CCTray > project (actually I'm using the OS-X variant, CCMenu) I get the > above error. I can browse the list of projects on the server OK, > and add a new one, but the status is just grey. > > The only difference I can see is that we're just using a straight- > up call to mongrel_rails to start the service, rather than using > 'cruise start'. Could that be the problem? I can't see anything > obvious in the source... > > cheers, > Matt > -------------- next part -------------- An HTML attachment was scrubbed... URL: From elijah.wright at gmail.com Mon Aug 18 15:01:02 2008 From: elijah.wright at gmail.com (elijah wright) Date: Mon, 18 Aug 2008 15:01:02 -0400 Subject: [Cruisecontrolrb-users] edits to database.yml make builds fail Message-ID: <2b4a11950808181201y74a7cacev42b3e94de9105e9@mail.gmail.com> Hi, We're seeing an issue where edits to database.yml - even edits that don't affect environments/branches being monitored with cruisecontrolrb - cause builds to fail. Running "svn revert" on database.yml in the build tree fixes the builds, oddly enough. Can someone, quick-and-dirty, explain what causes this, so that we better understand why it breaks our builds? :-) thanks, --elijah From thewoolleyman at gmail.com Mon Aug 18 15:51:29 2008 From: thewoolleyman at gmail.com (Chad Woolley) Date: Mon, 18 Aug 2008 12:51:29 -0700 Subject: [Cruisecontrolrb-users] edits to database.yml make builds fail In-Reply-To: <2b4a11950808181201y74a7cacev42b3e94de9105e9@mail.gmail.com> References: <2b4a11950808181201y74a7cacev42b3e94de9105e9@mail.gmail.com> Message-ID: On Mon, Aug 18, 2008 at 12:01 PM, elijah wright wrote: > We're seeing an issue where edits to database.yml - even edits that > don't affect environments/branches being monitored with > cruisecontrolrb - cause builds to fail. Can you give more detail on the failures? From matt at mattwynne.net Mon Aug 18 16:13:03 2008 From: matt at mattwynne.net (Matt Wynne) Date: Mon, 18 Aug 2008 21:13:03 +0100 Subject: [Cruisecontrolrb-users] edits to database.yml make builds fail In-Reply-To: <2b4a11950808181201y74a7cacev42b3e94de9105e9@mail.gmail.com> References: <2b4a11950808181201y74a7cacev42b3e94de9105e9@mail.gmail.com> Message-ID: <330031A2-1BC2-4D31-880D-1A2DD069404D@mattwynne.net> Could it be to do with the development database you're pointing to in your database.yml? I had some issues - mostly due to my naivety with the rails framework - around what happened to database schemas when the rake tasks ran to run our tests - it was stomping over the CI environment's test database with the schema from somewhere else... hope that's helpful... Matt On 18 Aug 2008, at 20:01, elijah wright wrote: > Hi, > > We're seeing an issue where edits to database.yml - even edits that > don't affect environments/branches being monitored with > cruisecontrolrb - cause builds to fail. > > Running "svn revert" on database.yml in the build tree fixes the > builds, oddly enough. > > Can someone, quick-and-dirty, explain what causes this, so that we > better understand why it breaks our builds? :-) > > thanks, > > --elijah > _______________________________________________ > Cruisecontrolrb-users mailing list > Cruisecontrolrb-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users From duelin.markers at gmail.com Mon Aug 18 19:20:16 2008 From: duelin.markers at gmail.com (John D. Hume) Date: Mon, 18 Aug 2008 19:20:16 -0400 Subject: [Cruisecontrolrb-users] edits to database.yml make builds fail In-Reply-To: <2b4a11950808181201y74a7cacev42b3e94de9105e9@mail.gmail.com> References: <2b4a11950808181201y74a7cacev42b3e94de9105e9@mail.gmail.com> Message-ID: Elijah, Do you have modifications in the cruise project's work directory (for example to point it at a different DB) that are leading to svn conflicts? I know you said it was happening with changes to environments that cruise doesn't care about, but I've definitely seen pain result from team members "solving" environment inconsistency problems by changing some environment config directly on the cruise server. (Don't do that.) -hume. From thewoolleyman at gmail.com Mon Aug 18 20:45:16 2008 From: thewoolleyman at gmail.com (Chad Woolley) Date: Mon, 18 Aug 2008 17:45:16 -0700 Subject: [Cruisecontrolrb-users] edits to database.yml make builds fail In-Reply-To: References: <2b4a11950808181201y74a7cacev42b3e94de9105e9@mail.gmail.com> Message-ID: On Mon, Aug 18, 2008 at 4:20 PM, John D. Hume wrote: > Elijah, > Do you have modifications in the cruise project's work directory (for > example to point it at a different DB) that are leading to svn > conflicts? > > I know you said it was happening with changes to environments that > cruise doesn't care about, but I've definitely seen pain result from > team members "solving" environment inconsistency problems by changing > some environment config directly on the cruise server. (Don't do > that.) Yep. To avoid this, you can leverage ERB to either have conditionals based on hostname, or read proper values from ENV variables or svn:ignored custom config files.. From will.sargent at gmail.com Mon Aug 18 23:12:35 2008 From: will.sargent at gmail.com (Will Sargent) Date: Mon, 18 Aug 2008 20:12:35 -0700 Subject: [Cruisecontrolrb-users] Competive Matrix of CI tools Message-ID: Hi guys, Thought you may be interested: note that cc.rb does NOT show up on this list... http://confluence.public.thoughtworks.org/display/CC/CI+Feature+Matrix Will. From thewoolleyman at gmail.com Tue Aug 19 00:46:47 2008 From: thewoolleyman at gmail.com (Chad Woolley) Date: Mon, 18 Aug 2008 21:46:47 -0700 Subject: [Cruisecontrolrb-users] Competive Matrix of CI tools In-Reply-To: References: Message-ID: On Mon, Aug 18, 2008 at 8:12 PM, Will Sargent wrote: > Hi guys, > > Thought you may be interested: note that cc.rb does NOT show up on this list... > > http://confluence.public.thoughtworks.org/display/CC/CI+Feature+Matrix Well, we'll have to fix that. I've got an account on there. Unfortunately, looking at the wiki markup for that page makes my eyes bleed... -- Chad From alexey.verkhovsky at gmail.com Tue Aug 19 01:00:17 2008 From: alexey.verkhovsky at gmail.com (Alexey Verkhovsky) Date: Mon, 18 Aug 2008 23:00:17 -0600 Subject: [Cruisecontrolrb-users] Competive Matrix of CI tools In-Reply-To: References: Message-ID: <3945c4270808182200o1e119567me8e09006940cf36e@mail.gmail.com> On Mon, Aug 18, 2008 at 10:46 PM, Chad Woolley wrote: >> Thought you may be interested: note that cc.rb does NOT show up on this list... >> http://confluence.public.thoughtworks.org/display/CC/CI+Feature+Matrix I think, the biggest thing I've personally learned from DamageControl was not paying too much attention to that matrix :) -- Alex From epugh at opensourceconnections.com Tue Aug 19 15:42:36 2008 From: epugh at opensourceconnections.com (Eric Pugh) Date: Tue, 19 Aug 2008 15:42:36 -0400 Subject: [Cruisecontrolrb-users] Competive Matrix of CI tools In-Reply-To: <3945c4270808182200o1e119567me8e09006940cf36e@mail.gmail.com> References: <3945c4270808182200o1e119567me8e09006940cf36e@mail.gmail.com> Message-ID: I have added CC.rb to the Matrix document. Eric On Tue, Aug 19, 2008 at 1:00 AM, Alexey Verkhovsky wrote: > On Mon, Aug 18, 2008 at 10:46 PM, Chad Woolley wrote: >>> Thought you may be interested: note that cc.rb does NOT show up on this list... >>> http://confluence.public.thoughtworks.org/display/CC/CI+Feature+Matrix > > I think, the biggest thing I've personally learned from DamageControl > was not paying too much attention to that matrix :) > > -- Alex > _______________________________________________ > Cruisecontrolrb-users mailing list > Cruisecontrolrb-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users > From alexey.verkhovsky at gmail.com Tue Aug 19 17:05:19 2008 From: alexey.verkhovsky at gmail.com (Alexey Verkhovsky) Date: Tue, 19 Aug 2008 15:05:19 -0600 Subject: [Cruisecontrolrb-users] Competive Matrix of CI tools In-Reply-To: References: <3945c4270808182200o1e119567me8e09006940cf36e@mail.gmail.com> Message-ID: <3945c4270808191405g1d269581rcdba2f9bc466fc76@mail.gmail.com> On Tue, Aug 19, 2008 at 1:42 PM, Eric Pugh wrote: > I have added CC.rb to the Matrix document. Thank you! :) -- Alex From rajiv at brontes3d.com Tue Aug 19 16:38:10 2008 From: rajiv at brontes3d.com (Rajiv Aaron Manglani) Date: Tue, 19 Aug 2008 16:38:10 -0400 Subject: [Cruisecontrolrb-users] Competive Matrix of CI tools In-Reply-To: References: <3945c4270808182200o1e119567me8e09006940cf36e@mail.gmail.com> Message-ID: <5C2A41DE-B221-49D7-8BE5-14C1E14DBD34@brontes3d.com> >> On Mon, Aug 18, 2008 at 10:46 PM, Chad Woolley > > wrote: >>>> Thought you may be interested: note that cc.rb does NOT show up >>>> on this list... >>>> http://confluence.public.thoughtworks.org/display/CC/CI+Feature+Matrix >> http://bitten.edgewall.org/ is missing as well. From epugh at opensourceconnections.com Wed Aug 20 06:35:44 2008 From: epugh at opensourceconnections.com (Eric Pugh) Date: Wed, 20 Aug 2008 06:35:44 -0400 Subject: [Cruisecontrolrb-users] Supporting different users checking out from SVN.. Message-ID: I think this is more of a SVN issue then a CC.rb issue, but hoping I can fix it via the cruise_config.rb file! I have been checking out projects on the build server using user "epugh", with the password stored in the .subversion directory. I did it by doing cruise -add and passing the --username and --password settings. However, I just added a new project from a new repository using user "ciuser" with a different password and now the older projects are trying to connect using user "ciuser" as well, but they don't have access: "svn: PROPFIND request failed on '/osc/hightechcville/trunk'' Any way to support a user per project? Eric From nicholas.faiz at gmail.com Thu Aug 21 18:55:49 2008 From: nicholas.faiz at gmail.com (Nicholas Faiz) Date: Fri, 22 Aug 2008 08:55:49 +1000 Subject: [Cruisecontrolrb-users] custom build scripts Message-ID: <48ADF275.1020307@gmail.com> Hello, Before I begin I should say that I'm using a forked version of ccrb which incorporates git access. It's available here: git://github.com/benburkert/cruisecontrolrb.git I'm trying to trigger a shell script in my cruise_config.rb . Well, I know it's running, as I leave a log of the activities of the script. Trouble is, the build doesn't finish. Has anyone else seen this sort of problem? I'm aware it could be to do with the fork itself, but I was just wondering how people were coping with building git projects in the absence of the forthcoming ccrb release. A relevant snippet from my config: # Build the project by invoking rake task 'custom' # project.rake_task = 'custom' # Specify the branch you're testing # This needs to be set if you used the -b option to cruse add # project.source_control.branch = 'release' # Build the project by invoking shell script "build_my_app.sh". Keep in mind that when the script is invoked, # current working directory is [cruise data]/projects/your_project/work, so if you do not keep build_my_app.sh # in version control, it should be '../build_my_app.sh' instead project.build_command = '../lhmu_build.sh' The script itself: #!/bin/sh cd work rm lhmu_build.log touch lhmu_build.log python bootstrap.py >> lhmu_build.log #bin/buildout >> lhmu_build.log #bin/instance test -s lhmu >> lhmu_build.log echo "finished!" >> lhmu_build.log exit 0 ~ And, as I mentioned, the logs verify the lhmu_build.sh script. As a side note, the git commands worked on my work's git repository after I put in a small workaround, so if anyone is interested in it, let me know. Regards, Nicholas From jeremy.lightsmith at gmail.com Thu Aug 21 18:59:46 2008 From: jeremy.lightsmith at gmail.com (Jeremy Lightsmith) Date: Thu, 21 Aug 2008 15:59:46 -0700 Subject: [Cruisecontrolrb-users] custom build scripts In-Reply-To: <48ADF275.1020307@gmail.com> References: <48ADF275.1020307@gmail.com> Message-ID: <648eacf20808211559k387e9066ved5751ec22d99717@mail.gmail.com> actually, the current version of cruise in development does support git. I believe the fork you're using uses a different strategy for git support than we do, so there may be some different behavior on corner cases. if you'd like to see if this is still happening to you with vanilla cruise, our code is at: git://github.com/thoughtworks/cruisecontrolrb.git I'm not sure what you'll need to do to switch, I don't know how far the code has diverged, I'd back up everything you have for your cruise stuff now before switching. Jeremy On Thu, Aug 21, 2008 at 3:55 PM, Nicholas Faiz wrote: > Hello, > > Before I begin I should say that I'm using a forked version of ccrb which > incorporates git access. It's available here: git:// > github.com/benburkert/cruisecontrolrb.git > > I'm trying to trigger a shell script in my cruise_config.rb . Well, I know > it's running, as I leave a log of the activities of the script. Trouble is, > the build doesn't finish. > > Has anyone else seen this sort of problem? I'm aware it could be to do with > the fork itself, but I was just wondering how people were coping with > building git projects in the absence of the forthcoming ccrb release. > > A relevant snippet from my config: > > # Build the project by invoking rake task 'custom' > # project.rake_task = 'custom' > > # Specify the branch you're testing > # This needs to be set if you used the -b option to cruse add > # project.source_control.branch = 'release' > > # Build the project by invoking shell script "build_my_app.sh". Keep in > mind that when the script is invoked, > # current working directory is > [cruise data]/projects/your_project/work, so if you do not > keep build_my_app.sh > # in version control, it should be '../build_my_app.sh' instead > project.build_command = '../lhmu_build.sh' > > > The script itself: > > #!/bin/sh > cd work > > rm lhmu_build.log > touch lhmu_build.log > python bootstrap.py >> lhmu_build.log > #bin/buildout >> lhmu_build.log > #bin/instance test -s lhmu >> lhmu_build.log > > echo "finished!" >> lhmu_build.log > > exit 0 > ~ > And, as I mentioned, the logs verify the lhmu_build.sh script. > > As a side note, the git commands worked on my work's git repository after I > put in a small workaround, so if anyone is interested in it, let me know. > > Regards, > Nicholas > > > > _______________________________________________ > Cruisecontrolrb-users mailing list > Cruisecontrolrb-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: From thewoolleyman at gmail.com Thu Aug 21 19:11:32 2008 From: thewoolleyman at gmail.com (Chad Woolley) Date: Thu, 21 Aug 2008 16:11:32 -0700 Subject: [Cruisecontrolrb-users] custom build scripts In-Reply-To: <648eacf20808211559k387e9066ved5751ec22d99717@mail.gmail.com> References: <48ADF275.1020307@gmail.com> <648eacf20808211559k387e9066ved5751ec22d99717@mail.gmail.com> Message-ID: On Thu, Aug 21, 2008 at 3:59 PM, Jeremy Lightsmith wrote: > actually, the current version of cruise in development does support git. I > believe the fork you're using uses a different strategy for git support than > we do, so there may be some different behavior on corner cases. The trunk support for git is definitely not ready for prime time. I'm using it to try to get the Rails CI box up again, and it was just hung for like a month trying to do a git merge. Had to manually kill the build and command process. I've opened several tickets tagged with git, and put a ticket on the list, no response yet. There have been several other git-related threads too. Even worse, benburkert's branch is off the old rubyforge Git repo, and not a "real" fork of the new github repo for ccrb. I've emailed benburkert off-list about maybe having him re-fork off the official one, but got no response. That is bad, because that means his branch is essentially frozen at the point he branched and not getting any new stuff. If I remember, Alexey's original objection to this branch was that Grit used native calls, and Alexey preferred to just use the command line to be more cross-platform. So, that is in and sort of working, but needs a lot more work, obviously. It would be great if someone stepped up and did that work, and these divergent git forks went away. Unfortunately, I'm not that person... -- Chad From nicholas.faiz at gmail.com Thu Aug 21 19:39:36 2008 From: nicholas.faiz at gmail.com (Nicholas Faiz) Date: Fri, 22 Aug 2008 09:39:36 +1000 Subject: [Cruisecontrolrb-users] custom build scripts In-Reply-To: References: <48ADF275.1020307@gmail.com> <648eacf20808211559k387e9066ved5751ec22d99717@mail.gmail.com> Message-ID: <48ADFCB8.4080704@gmail.com> Hi, I might give it a go, thanks for your reply. Even if I have to clone and checkout from scratch once a day, it's an improvement. We have no test and build visibility right now. The objection you point out to the fork is interesting, because the way I made it work was to force it to use the command line stuff (I think, it was a quick hack). And, yeh, I'm not that person you mention either. Cheers, Nicholas Chad Woolley wrote: > On Thu, Aug 21, 2008 at 3:59 PM, Jeremy Lightsmith > wrote: > >> actually, the current version of cruise in development does support git. I >> believe the fork you're using uses a different strategy for git support than >> we do, so there may be some different behavior on corner cases. >> > > The trunk support for git is definitely not ready for prime time. I'm > using it to try to get the Rails CI box up again, and it was just hung > for like a month trying to do a git merge. Had to manually kill the > build and command process. > > I've opened several tickets tagged with git, and put a ticket on the > list, no response yet. There have been several other git-related > threads too. > > Even worse, benburkert's branch is off the old rubyforge Git repo, and > not a "real" fork of the new github repo for ccrb. I've emailed > benburkert off-list about maybe having him re-fork off the official > one, but got no response. That is bad, because that means his branch > is essentially frozen at the point he branched and not getting any new > stuff. > > If I remember, Alexey's original objection to this branch was that > Grit used native calls, and Alexey preferred to just use the command > line to be more cross-platform. So, that is in and sort of working, > but needs a lot more work, obviously. It would be great if someone > stepped up and did that work, and these divergent git forks went away. > Unfortunately, I'm not that person... > > -- Chad > _______________________________________________ > Cruisecontrolrb-users mailing list > Cruisecontrolrb-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users > > From nicholas.faiz at gmail.com Thu Aug 21 19:44:31 2008 From: nicholas.faiz at gmail.com (Nicholas Faiz) Date: Fri, 22 Aug 2008 09:44:31 +1000 Subject: [Cruisecontrolrb-users] custom build scripts In-Reply-To: <648eacf20808211559k387e9066ved5751ec22d99717@mail.gmail.com> References: <48ADF275.1020307@gmail.com> <648eacf20808211559k387e9066ved5751ec22d99717@mail.gmail.com> Message-ID: <48ADFDDF.2040601@gmail.com> Thanks Jeremy - I'll check it out later today. It's my best bet, I think. Nicholas Jeremy Lightsmith wrote: > actually, the current version of cruise in development does support > git. I believe the fork you're using uses a different strategy for > git support than we do, so there may be some different behavior on > corner cases. > > if you'd like to see if this is still happening to you with vanilla > cruise, our code is at: > > git://github.com/thoughtworks/cruisecontrolrb.git > > > I'm not sure what you'll need to do to switch, I don't know how far > the code has diverged, I'd back up everything you have for your cruise > stuff now before switching. > > Jeremy > > On Thu, Aug 21, 2008 at 3:55 PM, Nicholas Faiz > > wrote: > > Hello, > > Before I begin I should say that I'm using a forked version of > ccrb which incorporates git access. It's available here: > git://github.com/benburkert/cruisecontrolrb.git > > > I'm trying to trigger a shell script in my cruise_config.rb . > Well, I know it's running, as I leave a log of the activities of > the script. Trouble is, the build doesn't finish. > > Has anyone else seen this sort of problem? I'm aware it could be > to do with the fork itself, but I was just wondering how people > were coping with building git projects in the absence of the > forthcoming ccrb release. > > A relevant snippet from my config: > > # Build the project by invoking rake task 'custom' > # project.rake_task = 'custom' > > # Specify the branch you're testing > # This needs to be set if you used the -b option to cruse add > # project.source_control.branch = 'release' > > # Build the project by invoking shell script "build_my_app.sh". > Keep in mind that when the script is invoked, > # current working directory is > [cruise data]/projects/your_project/work, so if you > do not keep build_my_app.sh > # in version control, it should be '../build_my_app.sh' instead > project.build_command = '../lhmu_build.sh' > > > The script itself: > > #!/bin/sh > cd work > > rm lhmu_build.log > touch lhmu_build.log > python bootstrap.py >> lhmu_build.log > #bin/buildout >> lhmu_build.log > #bin/instance test -s lhmu >> lhmu_build.log > > echo "finished!" >> lhmu_build.log > > exit 0 > ~ > And, as I mentioned, the logs verify the lhmu_build.sh script. > > As a side note, the git commands worked on my work's git > repository after I put in a small workaround, so if anyone is > interested in it, let me know. > > Regards, > Nicholas > > > > _______________________________________________ > Cruisecontrolrb-users mailing list > Cruisecontrolrb-users at rubyforge.org > > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users > > > ------------------------------------------------------------------------ > > _______________________________________________ > Cruisecontrolrb-users mailing list > Cruisecontrolrb-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users > From nicholas.faiz at gmail.com Fri Aug 22 06:28:16 2008 From: nicholas.faiz at gmail.com (Nicholas Faiz) Date: Fri, 22 Aug 2008 20:28:16 +1000 Subject: [Cruisecontrolrb-users] git + Re: custom build scripts In-Reply-To: References: <48ADF275.1020307@gmail.com> <648eacf20808211559k387e9066ved5751ec22d99717@mail.gmail.com> Message-ID: <48AE94C0.5030006@gmail.com> Hi, Just to let you know that I did finally get benburket's fork to work with git. It took a little hacking into what he had, and understanding git + ssh key auth intricacies, but it's running. If anyone else is stuck I can share my config.. Regards, Nicholas Chad Woolley wrote: > On Thu, Aug 21, 2008 at 3:59 PM, Jeremy Lightsmith > wrote: > >> actually, the current version of cruise in development does support git. I >> believe the fork you're using uses a different strategy for git support than >> we do, so there may be some different behavior on corner cases. >> > > The trunk support for git is definitely not ready for prime time. I'm > using it to try to get the Rails CI box up again, and it was just hung > for like a month trying to do a git merge. Had to manually kill the > build and command process. > > I've opened several tickets tagged with git, and put a ticket on the > list, no response yet. There have been several other git-related > threads too. > > Even worse, benburkert's branch is off the old rubyforge Git repo, and > not a "real" fork of the new github repo for ccrb. I've emailed > benburkert off-list about maybe having him re-fork off the official > one, but got no response. That is bad, because that means his branch > is essentially frozen at the point he branched and not getting any new > stuff. > > If I remember, Alexey's original objection to this branch was that > Grit used native calls, and Alexey preferred to just use the command > line to be more cross-platform. So, that is in and sort of working, > but needs a lot more work, obviously. It would be great if someone > stepped up and did that work, and these divergent git forks went away. > Unfortunately, I'm not that person... > > -- Chad > _______________________________________________ > Cruisecontrolrb-users mailing list > Cruisecontrolrb-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users > > From thewoolleyman at gmail.com Fri Aug 22 12:42:52 2008 From: thewoolleyman at gmail.com (Chad Woolley) Date: Fri, 22 Aug 2008 09:42:52 -0700 Subject: [Cruisecontrolrb-users] git + Re: custom build scripts In-Reply-To: <48AE94C0.5030006@gmail.com> References: <48ADF275.1020307@gmail.com> <648eacf20808211559k387e9066ved5751ec22d99717@mail.gmail.com> <48AE94C0.5030006@gmail.com> Message-ID: On Fri, Aug 22, 2008 at 3:28 AM, Nicholas Faiz wrote: > Hi, > > Just to let you know that I did finally get benburket's fork to work with > git. It took a little hacking into what he had, and understanding git + ssh > key auth intricacies, but it's running. If anyone else is stuck I can share > my config.. Sure. It's a fork on Github, right? Just send the link... From peter.fitzgibbons at gmail.com Fri Aug 22 15:46:08 2008 From: peter.fitzgibbons at gmail.com (Peter Fitzgibbons) Date: Fri, 22 Aug 2008 14:46:08 -0500 Subject: [Cruisecontrolrb-users] rake abort -- CC.rb build succeeded! Message-ID: <670a00380808221246x5ddc07abh8a827c43c6f00417@mail.gmail.com> Hello all. I have a project whose rake aborts in the current svn revision, a-la : cruisecontrol at test:~/.cruise/projects/Myprojectwork$ rake (in /home/cruisecontrol/.cruise/projects/Myproject/work) /usr/local/bin/ruby -Ilib:test "/usr/local/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake/rake_test_loader.rb" /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in `gem_original_require': /home/cruisecontrol/.cruise/projects/Myprojectwork/app/models/customer_quote.rb:3: syntax error, unexpected kEND, expecting $end (SyntaxError) from /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in `require' [... yadda yadda ...] rake aborted! Command /usr/local/bin/ruby -I [... yadda yadda ... ] failed The rake "should" be aborting for me, as the customer_quote.rb is : xxclass CustomerQuote; end which has obvious syntax errors. yet, builder reports success, from console log of ./cruise start --trace [debug] /home/cruisecontrol/.cruise/projects/Myproject/work cruisecontrol$ svn --non-interactive update --revision 46 [info] [2008-08-22 14:44:22] Build 46.1 started Build 46.1 started ./script/../config/../vendor/rails/railties/lib/webrick_server.rb:71: warning: conflicting chdir during another chdir block 192.168.0.49 - - [22/Aug/2008:14:44:22 CDT] "GET /projects.js HTTP/1.1" 200 2428 http://test:3333/ -> /projects.js [debug] [2008-08-22 14:44:24] Sending e-mail to 1 person [... yadda email ...] [debug] [2008-08-22 14:44:24] Sent e-mail to 1 person [info] [2008-08-22 14:44:24] Build 46.1 finished SUCCESSFULLY Build 46.1 finished SUCCESSFULLY Does anyone have a patch for this .... or can direct me to which method call I can hack to make an aborted rake == build fail ? Thanks ! Peter Fitzgibbons (847) 687-7646 Email: peter.fitzgibbons at gmail.com IM GTalk: peter.fitzgibbons IM Yahoo: pjfitzgibbons IM MSN: pjfitzgibbons at hotmail.com IM AOL: peter.fitzgibbons at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From jeremy.lightsmith at gmail.com Fri Aug 22 16:34:38 2008 From: jeremy.lightsmith at gmail.com (Jeremy Lightsmith) Date: Fri, 22 Aug 2008 13:34:38 -0700 Subject: [Cruisecontrolrb-users] rake abort -- CC.rb build succeeded! In-Reply-To: <670a00380808221246x5ddc07abh8a827c43c6f00417@mail.gmail.com> References: <670a00380808221246x5ddc07abh8a827c43c6f00417@mail.gmail.com> Message-ID: <648eacf20808221334y79a377efgd8a74550df745450@mail.gmail.com> can we see your cruise_config.rb file? or if you have a custom cruise task, can we see that? I would try to do exactly what cruise is doing, and then typing "echo $?" this will give you the exit code of the last command run. all cruise does is rail the build if the exit code is not zero. rake should (and always has when I've played with it) return a nonzero exit code when there is an exception thrown inside it. however, if you are calling other processes from your own and not propagating exceptions, then you're hiding that error from cruise. Jeremy On Fri, Aug 22, 2008 at 12:46 PM, Peter Fitzgibbons < peter.fitzgibbons at gmail.com> wrote: > Hello all. > > I have a project whose rake aborts in the current svn revision, a-la : > > cruisecontrol at test:~/.cruise/projects/Myprojectwork$ rake > (in /home/cruisecontrol/.cruise/projects/Myproject/work) > /usr/local/bin/ruby -Ilib:test > "/usr/local/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake/rake_test_loader.rb" > > /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in > `gem_original_require': > /home/cruisecontrol/.cruise/projects/Myprojectwork/app/models/customer_quote.rb:3: > syntax error, unexpected kEND, expecting $end (SyntaxError) > from /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in > `require' > [... yadda yadda ...] > rake aborted! > Command /usr/local/bin/ruby -I [... yadda yadda ... ] failed > > The rake "should" be aborting for me, as the customer_quote.rb is : xxclass > CustomerQuote; end which has obvious syntax errors. > > yet, builder reports success, from console log of ./cruise start --trace > [debug] /home/cruisecontrol/.cruise/projects/Myproject/work cruisecontrol$ > svn --non-interactive update --revision 46 > [info] [2008-08-22 14:44:22] Build 46.1 started > Build 46.1 started > ./script/../config/../vendor/rails/railties/lib/webrick_server.rb:71: > warning: conflicting chdir during another chdir block > 192.168.0.49 - - [22/Aug/2008:14:44:22 CDT] "GET /projects.js HTTP/1.1" > 200 2428 > http://test:3333/ -> /projects.js > [debug] [2008-08-22 14:44:24] Sending e-mail to 1 person > [... yadda email ...] > [debug] [2008-08-22 14:44:24] Sent e-mail to 1 person > [info] [2008-08-22 14:44:24] Build 46.1 finished SUCCESSFULLY > Build 46.1 finished SUCCESSFULLY > > Does anyone have a patch for this .... or can direct me to which method > call I can hack to make an aborted rake == build fail ? > > Thanks ! > > > Peter Fitzgibbons > (847) 687-7646 > Email: peter.fitzgibbons at gmail.com > IM GTalk: peter.fitzgibbons > IM Yahoo: pjfitzgibbons > IM MSN: pjfitzgibbons at hotmail.com > IM AOL: peter.fitzgibbons at gmail.com > > _______________________________________________ > Cruisecontrolrb-users mailing list > Cruisecontrolrb-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From thewoolleyman at gmail.com Fri Aug 22 20:55:13 2008 From: thewoolleyman at gmail.com (Chad Woolley) Date: Fri, 22 Aug 2008 17:55:13 -0700 Subject: [Cruisecontrolrb-users] Competive Matrix of CI tools In-Reply-To: References: <3945c4270808182200o1e119567me8e09006940cf36e@mail.gmail.com> Message-ID: On Tue, Aug 19, 2008 at 12:42 PM, Eric Pugh wrote: > I have added CC.rb to the Matrix document. > > Eric I was thinking - there should be another icon to represent an Open source or Plugin-Based architecture - meaning that even though a feature does not exist, it can be added via a plugin or modification of the source. This is a big advantage over Closed-Source tools or tools which do not support Plugins. -- Chad From epugh at opensourceconnections.com Sat Aug 23 07:58:49 2008 From: epugh at opensourceconnections.com (Eric Pugh) Date: Sat, 23 Aug 2008 07:58:49 -0400 Subject: [Cruisecontrolrb-users] Competive Matrix of CI tools In-Reply-To: References: <3945c4270808182200o1e119567me8e09006940cf36e@mail.gmail.com> Message-ID: So, I like what Chad is proposing, but the lesson I learned adding CC.rb to the matrix is that the more data you put into the chart, the less valuable it is... If you look at it as "Whever has the most green icons wins", then you get the one size fits all solution... And adding more options means that it makes it harder and harder to use. CC.rb is arguably the best solution for doing SVN based Ruby builds. But that isn't really reflected in that long list... I almost wonder if we need a summary and then a detail page.. Cause right now, looking at the page today, I am drowning in details! Eric On Fri, Aug 22, 2008 at 8:55 PM, Chad Woolley wrote: > On Tue, Aug 19, 2008 at 12:42 PM, Eric Pugh > wrote: >> I have added CC.rb to the Matrix document. >> >> Eric > > I was thinking - there should be another icon to represent an Open > source or Plugin-Based architecture - meaning that even though a > feature does not exist, it can be added via a plugin or modification > of the source. > > This is a big advantage over Closed-Source tools or tools which do not > support Plugins. > > -- Chad > _______________________________________________ > Cruisecontrolrb-users mailing list > Cruisecontrolrb-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users > From thewoolleyman at gmail.com Sun Aug 24 02:15:43 2008 From: thewoolleyman at gmail.com (Chad Woolley) Date: Sat, 23 Aug 2008 23:15:43 -0700 Subject: [Cruisecontrolrb-users] [ANN] Cinabox: Continuous Integration - in a Box! Message-ID: Hi, Here's a project I made that will hopefully make it easier for people to adopt CCRB: http://github.com/thewoolleyman/cinabox/tree/master/README.txt There's also a screencast: http://s3.amazonaws.com/assets.pivotallabs.com/99/original/cinabox_screencast.mov ...and blog post: http://pivots.pivotallabs.com/users/chad/blog/articles/471-continuous-integration-in-a-box-exploring-tsttcpw Comments welcome... Thanks, -- Chad From gigix1980 at gmail.com Sun Aug 24 04:45:29 2008 From: gigix1980 at gmail.com (Jeff Xiong) Date: Sun, 24 Aug 2008 16:45:29 +0800 Subject: [Cruisecontrolrb-users] [ANN] Cinabox: Continuous Integration - in a Box! In-Reply-To: References: Message-ID: <20fd9dc50808240145u147d5de8pdfca8496dac36d5e@mail.gmail.com> Just a suggestion: do you think it's valuable to install CC.rb and RubyWorks production stack (plus infrastructures such as SVN) in a box and make it a virtual machine, just like Buildix? On Sun, Aug 24, 2008 at 2:15 PM, Chad Woolley wrote: > Hi, > > Here's a project I made that will hopefully make it easier for people > to adopt CCRB: > > http://github.com/thewoolleyman/cinabox/tree/master/README.txt > > There's also a screencast: > http://s3.amazonaws.com/assets.pivotallabs.com/99/original/cinabox_screencast.mov > > ...and blog post: > http://pivots.pivotallabs.com/users/chad/blog/articles/471-continuous-integration-in-a-box-exploring-tsttcpw > > Comments welcome... > > Thanks, > -- Chad > _______________________________________________ > Cruisecontrolrb-users mailing list > Cruisecontrolrb-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users > -- Jeff Xiong Software Journeyman - http://gigix.thoughtworkers.org Open Source Contributor - http://fluorida.googlecode.com/ Technical Evangelist - http://www.infoq.com/cn/ From thewoolleyman at gmail.com Sun Aug 24 04:59:41 2008 From: thewoolleyman at gmail.com (Chad Woolley) Date: Sun, 24 Aug 2008 01:59:41 -0700 Subject: [Cruisecontrolrb-users] [ANN] Cinabox: Continuous Integration - in a Box! In-Reply-To: <20fd9dc50808240145u147d5de8pdfca8496dac36d5e@mail.gmail.com> References: <20fd9dc50808240145u147d5de8pdfca8496dac36d5e@mail.gmail.com> Message-ID: On Sun, Aug 24, 2008 at 1:45 AM, Jeff Xiong wrote: > Just a suggestion: do you think it's valuable to install CC.rb and > RubyWorks production stack (plus infrastructures such as SVN) in a box > and make it a virtual machine, just like Buildix? Thanks for the response Jeff. First, I don't want to do anything with static VM images like Buildix. That's too hard to maintain, as least for a non-employer-subsidized OSS project like Cinabox. I've maintained my share of VM Images, and I'd prefer to stab myself in the eye with a fork over doing that long-term. Instead, the idea behind Cinabox is to start with a known environment (I picked Ubuntu 8.04 and MRI), and have a couple of scripts which do everything else for you. The benefit of this approach is that you can re-run them in the future to update things. For example, cinabox's setup_ci.rb will always update to the latest ccrb, and will re-install all other packages if you pass --force. As for the RubyWorks stack, I see that as just another environment (RHEL/CentOS/JRuby) to target in addition to Ubuntu/MRI. I'm envisioning an "alternate_environments" subdirectory which will contain subdirectories scripts specific to these environments - such as a CentOS-JRuby subdir with a specific bootstrap_jruby.sh and setup_ci.rb. Or even RubyWorks- or Buildix-specific environments. -- Chad From shankernayak at gmail.com Tue Aug 26 10:24:23 2008 From: shankernayak at gmail.com (Shanker Nayak) Date: Tue, 26 Aug 2008 19:54:23 +0530 Subject: [Cruisecontrolrb-users] Install error Message-ID: Hi all, I am getting error during installation of cruise, I am trying to add a project D:\ir\rails_apps\pronew\cruise>cruise add pronew --url http://xxx.xxx.0.xxx/pro/pro --username yyyy --password tttt below I have copy pasted the error from the command prompt, the project trunk directory is located at http://xxx.xxx.0.xxx/pro/pro, can someone please help so as to what I am doing wrong . cruise data root = 'D:\ir\rails_apps\pronew\cruise' Adding project 'pronew' (this may take a while)... No such file or directory - svn co http://xxx.xxx.0.xxx/pro/proD:/ir/rails_apps/pronew/cruise/projects/pronew/work --username yyyy --password tttt ./script/../config/../lib/command_line.rb:84:in `popen' ./script/../config/../lib/command_line.rb:84:in `e' ./script/../config/../lib/command_line.rb:71:in `execute' ./script/../config/../lib/command_line.rb:70:in `chdir' ./script/../config/../lib/command_line.rb:70:in `execute' ./script/../config/../lib/subversion.rb:136:in `execute_in_local_copy' ./script/../config/../lib/subversion.rb:127:in `svn' ./script/../config/../lib/subversion.rb:46:in `checkout' ./script/../config/../app/models/projects.rb:57:in `checkout_local_copy' ./script/../config/../app/models/projects.rb:40:in `<<' ./script/add_project:55 cruise:10:in `load' cruise:10:in `add' cruise:68:in `send' cruise:68 D:/ir/ruby/lib/ruby/1.8/fileutils.rb:121:in `chdir' D:/ir/ruby/lib/ruby/1.8/fileutils.rb:121:in `cd' cruise:67 FAILED: dir : D:/ir/rails_apps/pronew/cruise command : svncohttp://xxx.xxx.0.xxx/pro/proD:/ir/rails_apps/pronew/cruise/projects/ pronew/work--usernameyyyy--passwordtttt executed command : svn co http://xxx.xxx.0.xxx/pro/proD:/ir/rails_apps/pronew/crui se/projects/pronew/work --username yyyy --password tttt exitstatus: STDERR TAIL START No such file or directory - svn co http://xxx.xxx.0.xxx/pro/proD:/ir/rails_apps/m enew/cruise/projects/pronew/work --username yyyy --password tttt STDERR TAIL END regards, shaan -------------- next part -------------- An HTML attachment was scrubbed... URL: From matt at mattwynne.net Tue Aug 26 11:54:27 2008 From: matt at mattwynne.net (Matt Wynne) Date: Tue, 26 Aug 2008 16:54:27 +0100 Subject: [Cruisecontrolrb-users] Install error In-Reply-To: References: Message-ID: It sounds as though CC is trying to run that shell command (svn co ...) and failing. Is the svn command in the path for the user that CC is running under? Have you tried running the command in your own prompt to check for typos? i.e. >svn co http://xxx.xxx.0.xxx/pro/pro D:/ir/rails_apps/pronew/cruise/ projects/pronew/work --username yyyy --password tttt cheers, Matt ---- http://blog.mattwynne.net http://songkick.com In case you wondered: The opinions expressed in this email are my own and do not necessarily reflect the views of any former, current or future employers of mine. On 26 Aug 2008, at 15:24, Shanker Nayak wrote: > Hi all, > > I am getting error during installation of cruise, I am trying to > add a project > > D:\ir\rails_apps\pronew\cruise>cruise add pronew --url http:// > xxx.xxx.0.xxx/pro/pro --username yyyy --password tttt > > below I have copy pasted the error from the command prompt, the > project trunk directory is located at http://xxx.xxx.0.xxx/pro/pro, > can someone please help so as to what I am doing wrong . > > cruise data root = 'D:\ir\rails_apps\pronew\cruise' > Adding project 'pronew' (this may take a while)... > No such file or directory - svn co http://xxx.xxx.0.xxx/pro/pro D:/ > ir/rails_apps/pronew/cruise/projects/pronew/work --username yyyy -- > password tttt > ./script/../config/../lib/command_line.rb:84:in `popen' > ./script/../config/../lib/command_line.rb:84:in `e' > ./script/../config/../lib/command_line.rb:71:in `execute' > ./script/../config/../lib/command_line.rb:70:in `chdir' > ./script/../config/../lib/command_line.rb:70:in `execute' > ./script/../config/../lib/subversion.rb:136:in > `execute_in_local_copy' > ./script/../config/../lib/subversion.rb:127:in `svn' > ./script/../config/../lib/subversion.rb:46:in `checkout' > ./script/../config/../app/models/projects.rb:57:in > `checkout_local_copy' > ./script/../config/../app/models/projects.rb:40:in `<<' > ./script/add_project:55 > cruise:10:in `load' > cruise:10:in `add' > cruise:68:in `send' > cruise:68 > D:/ir/ruby/lib/ruby/1.8/fileutils.rb:121:in `chdir' > D:/ir/ruby/lib/ruby/1.8/fileutils.rb:121:in `cd' > cruise:67 > FAILED: > dir : D:/ir/rails_apps/pronew/cruise > command : svncohttp://xxx.xxx.0.xxx/pro/proD:/ir/rails_apps/pronew/ > cruise/projects/ > pronew/work--usernameyyyy--passwordtttt > executed command : svn co http://xxx.xxx.0.xxx/pro/pro D:/ir/ > rails_apps/pronew/crui > se/projects/pronew/work --username yyyy --password tttt > exitstatus: > STDERR TAIL START > No such file or directory - svn co http://xxx.xxx.0.xxx/pro/pro D:/ > ir/rails_apps/m > enew/cruise/projects/pronew/work --username yyyy --password tttt > STDERR TAIL END > > regards, > shaan > _______________________________________________ > Cruisecontrolrb-users mailing list > Cruisecontrolrb-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexey.verkhovsky at gmail.com Tue Aug 26 12:16:42 2008 From: alexey.verkhovsky at gmail.com (Alexey Verkhovsky) Date: Tue, 26 Aug 2008 10:16:42 -0600 Subject: [Cruisecontrolrb-users] Install error In-Reply-To: References: Message-ID: <3945c4270808260916k73df1f56s807a5cc0d616f18c@mail.gmail.com> This is a Windows bug in the latest release. Your choice is either downgrading to 1.2.1, or use the trunk. -- Alex On 8/26/08, Matt Wynne wrote: > It sounds as though CC is trying to run that shell command (svn > co ...) and failing. > > Is the svn command in the path for the user that CC is running under? > > Have you tried running the command in your own prompt to check for > typos? > > i.e. > > >svn co http://xxx.xxx.0.xxx/pro/pro D:/ir/rails_apps/pronew/cruise/ > projects/pronew/work --username yyyy --password tttt > > > cheers, > Matt > ---- > http://blog.mattwynne.net > http://songkick.com > > In case you wondered: The opinions expressed in this email are my own > and do not necessarily reflect the views of any former, current or > future employers of mine. > > > > On 26 Aug 2008, at 15:24, Shanker Nayak wrote: > >> Hi all, >> >> I am getting error during installation of cruise, I am trying to >> add a project >> >> D:\ir\rails_apps\pronew\cruise>cruise add pronew --url http:// >> xxx.xxx.0.xxx/pro/pro --username yyyy --password tttt >> >> below I have copy pasted the error from the command prompt, the >> project trunk directory is located at http://xxx.xxx.0.xxx/pro/pro, >> can someone please help so as to what I am doing wrong . >> >> cruise data root = 'D:\ir\rails_apps\pronew\cruise' >> Adding project 'pronew' (this may take a while)... >> No such file or directory - svn co http://xxx.xxx.0.xxx/pro/pro D:/ >> ir/rails_apps/pronew/cruise/projects/pronew/work --username yyyy -- >> password tttt >> ./script/../config/../lib/command_line.rb:84:in `popen' >> ./script/../config/../lib/command_line.rb:84:in `e' >> ./script/../config/../lib/command_line.rb:71:in `execute' >> ./script/../config/../lib/command_line.rb:70:in `chdir' >> ./script/../config/../lib/command_line.rb:70:in `execute' >> ./script/../config/../lib/subversion.rb:136:in >> `execute_in_local_copy' >> ./script/../config/../lib/subversion.rb:127:in `svn' >> ./script/../config/../lib/subversion.rb:46:in `checkout' >> ./script/../config/../app/models/projects.rb:57:in >> `checkout_local_copy' >> ./script/../config/../app/models/projects.rb:40:in `<<' >> ./script/add_project:55 >> cruise:10:in `load' >> cruise:10:in `add' >> cruise:68:in `send' >> cruise:68 >> D:/ir/ruby/lib/ruby/1.8/fileutils.rb:121:in `chdir' >> D:/ir/ruby/lib/ruby/1.8/fileutils.rb:121:in `cd' >> cruise:67 >> FAILED: >> dir : D:/ir/rails_apps/pronew/cruise >> command : svncohttp://xxx.xxx.0.xxx/pro/proD:/ir/rails_apps/pronew/ >> cruise/projects/ >> pronew/work--usernameyyyy--passwordtttt >> executed command : svn co http://xxx.xxx.0.xxx/pro/pro D:/ir/ >> rails_apps/pronew/crui >> se/projects/pronew/work --username yyyy --password tttt >> exitstatus: >> STDERR TAIL START >> No such file or directory - svn co http://xxx.xxx.0.xxx/pro/pro D:/ >> ir/rails_apps/m >> enew/cruise/projects/pronew/work --username yyyy --password tttt >> STDERR TAIL END >> >> regards, >> shaan >> _______________________________________________ >> Cruisecontrolrb-users mailing list >> Cruisecontrolrb-users at rubyforge.org >> http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users > > -- Alexey Verkhovsky CruiseControl.rb [http://cruisecontrolrb.thoughtworks.com] RubyWorks [http://rubyworks.thoughtworks.com] From brian at newmedio.com Thu Aug 28 10:08:09 2008 From: brian at newmedio.com (Higgaion) Date: Thu, 28 Aug 2008 07:08:09 -0700 (PDT) Subject: [Cruisecontrolrb-users] CruiseControlRb behind apache In-Reply-To: <80E840CA-EDDB-49B5-8684-FB321F8F7A12@gmail.com> References: <80E840CA-EDDB-49B5-8684-FB321F8F7A12@gmail.com> Message-ID: <19201355.post@talk.nabble.com> I share your goal. this block gets css and js links to work while hosting at a sub dir. AuthType Basic AuthName "CCRB" AuthUserFile /etc/httpd/conf.d/ccrb.htpasswd Require valid-user ProxyPass http://localhost:3333/ ProxyPassReverse http://localhost:3333/ however, all of the links within cc.rb try to jump back to '/'. ex: /projects works if i manually go to /ccrb/projects, but the links within cc.rb are all broken. any apache guru know how to trick cc.rb into thinking its root is '/ccrb/' instead of '/' ? Ketan Padegaonkar-2 wrote: > > However is there a better way for me to have cruise running under > http://myserver/cruise > instead of rooting it at "/". mod_proxy only rendered the html if I > did this because the stylesheets and javascripts were in "/javascript" > and "/stylesheets" instead of "/cruise/javascript" and "/cruise/ > javascipt". > > Is there a way I could run cruise under /cruise when starting it up, > so that my apache acts as a dumb proxy ? > > -- View this message in context: http://www.nabble.com/CruiseControlRb-behind-apache-tp17013243p19201355.html Sent from the CruiseControl.rb - Users mailing list archive at Nabble.com. From epugh at opensourceconnections.com Thu Aug 28 12:05:47 2008 From: epugh at opensourceconnections.com (Eric Pugh) Date: Thu, 28 Aug 2008 12:05:47 -0400 Subject: [Cruisecontrolrb-users] CruiseControlRb behind apache In-Reply-To: <19201355.post@talk.nabble.com> References: <80E840CA-EDDB-49B5-8684-FB321F8F7A12@gmail.com> <19201355.post@talk.nabble.com> Message-ID: I ended up using a plugin call HTPasswd to give me security.. For me it was much easier then mucking around with Apache. I blogged about it here: http://www.opensourceconnections.com/2008/08/28/securing-cc.rb-from-the-world/ Eric On Thu, Aug 28, 2008 at 10:08 AM, Higgaion wrote: > > I share your goal. this block gets css and js links to work while hosting at > a sub dir. > > AuthType Basic > AuthName "CCRB" > AuthUserFile /etc/httpd/conf.d/ccrb.htpasswd > Require valid-user > ProxyPass http://localhost:3333/ > ProxyPassReverse http://localhost:3333/ > > > however, all of the links within cc.rb try to jump back to '/'. ex: > /projects works if i manually go to /ccrb/projects, but the links within > cc.rb are all broken. any apache guru know how to trick cc.rb into thinking > its root is '/ccrb/' instead of '/' ? > > > > Ketan Padegaonkar-2 wrote: >> >> However is there a better way for me to have cruise running under >> http://myserver/cruise >> instead of rooting it at "/". mod_proxy only rendered the html if I >> did this because the stylesheets and javascripts were in "/javascript" >> and "/stylesheets" instead of "/cruise/javascript" and "/cruise/ >> javascipt". >> >> Is there a way I could run cruise under /cruise when starting it up, >> so that my apache acts as a dumb proxy ? >> >> > > -- > View this message in context: http://www.nabble.com/CruiseControlRb-behind-apache-tp17013243p19201355.html > Sent from the CruiseControl.rb - Users mailing list archive at Nabble.com. > > _______________________________________________ > Cruisecontrolrb-users mailing list > Cruisecontrolrb-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users > From brian at newmedio.com Thu Aug 28 15:14:33 2008 From: brian at newmedio.com (Higgaion) Date: Thu, 28 Aug 2008 12:14:33 -0700 (PDT) Subject: [Cruisecontrolrb-users] CruiseControlRb behind apache In-Reply-To: References: <80E840CA-EDDB-49B5-8684-FB321F8F7A12@gmail.com> <19201355.post@talk.nabble.com> Message-ID: <19207198.post@talk.nabble.com> that looks like a good approach to the security issue, but i want my ccrb to be publicly accessible on port 80 at a path. I could do this with one of my unused static ips and my firewall, but that seems like overkill if this can be done w/ apache. Eric Pugh-4 wrote: > > I ended up using a plugin call HTPasswd to give me security.. For me > it was much easier then mucking around with Apache. > > I blogged about it here: > http://www.opensourceconnections.com/2008/08/28/securing-cc.rb-from-the-world/ > > Eric > > > On Thu, Aug 28, 2008 at 10:08 AM, Higgaion wrote: >> >> I share your goal. this block gets css and js links to work while hosting >> at >> a sub dir. >> >> AuthType Basic >> AuthName "CCRB" >> AuthUserFile /etc/httpd/conf.d/ccrb.htpasswd >> Require valid-user >> ProxyPass http://localhost:3333/ >> ProxyPassReverse http://localhost:3333/ >> >> >> however, all of the links within cc.rb try to jump back to '/'. ex: >> /projects works if i manually go to /ccrb/projects, but the links within >> cc.rb are all broken. any apache guru know how to trick cc.rb into >> thinking >> its root is '/ccrb/' instead of '/' ? >> >> >> >> Ketan Padegaonkar-2 wrote: >>> >>> However is there a better way for me to have cruise running under >>> http://myserver/cruise >>> instead of rooting it at "/". mod_proxy only rendered the html if I >>> did this because the stylesheets and javascripts were in "/javascript" >>> and "/stylesheets" instead of "/cruise/javascript" and "/cruise/ >>> javascipt". >>> >>> Is there a way I could run cruise under /cruise when starting it up, >>> so that my apache acts as a dumb proxy ? >>> >>> >> >> -- >> View this message in context: >> http://www.nabble.com/CruiseControlRb-behind-apache-tp17013243p19201355.html >> Sent from the CruiseControl.rb - Users mailing list archive at >> Nabble.com. >> >> _______________________________________________ >> Cruisecontrolrb-users mailing list >> Cruisecontrolrb-users at rubyforge.org >> http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users >> > _______________________________________________ > Cruisecontrolrb-users mailing list > Cruisecontrolrb-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users > > -- View this message in context: http://www.nabble.com/CruiseControlRb-behind-apache-tp17013243p19207198.html Sent from the CruiseControl.rb - Users mailing list archive at Nabble.com. From matt at mattwynne.net Fri Aug 29 10:25:25 2008 From: matt at mattwynne.net (Matt Wynne) Date: Fri, 29 Aug 2008 15:25:25 +0100 Subject: [Cruisecontrolrb-users] Keeping CRUISE_DATA_ROUTE under version control Message-ID: <21A6E676-C754-4D6F-BCE7-07F697BF0DDC@mattwynne.net> I have a goal to allow any of us on the team to be able to fetch the build environment locally and run / hack it, them commit their changes back and be able to easily deploy them to the team's shared build environment. To that end, I've cloned the github repo for ccrb into a project in our private team repo, and then cloned that one onto my local machine. I made a folder /data inside the cruisecontrol.rb folder, and configured CRUISE_DATA_ROOT to point to that folder. I then added a couple of projects with cruise add. I didn't want the build history, or all the source for each project to be checked in with the build server code, so I excluded some files. We use git, so I added a .gitignore folder in data/projects like this: work build-* builder.* builder_status.* Now I'm trying to work out what I need to commit to the cruise git repo so that someone else could pull it and have all the projects. I guess excluding the whole /work folder was a bit heavy handed, because you need at least some of what's in work/.git in order for cruise to know where the project's repository is... or is this stored anywhere else? has anyone else tried to do this and succeeded? cheers, Matt ---- http://blog.mattwynne.net http://songkick.com In case you wondered: The opinions expressed in this email are my own and do not necessarily reflect the views of any former, current or future employers of mine. -------------- next part -------------- An HTML attachment was scrubbed... URL: From thewoolleyman at gmail.com Fri Aug 29 11:13:07 2008 From: thewoolleyman at gmail.com (Chad Woolley) Date: Fri, 29 Aug 2008 08:13:07 -0700 Subject: [Cruisecontrolrb-users] Keeping CRUISE_DATA_ROUTE under version control In-Reply-To: <21A6E676-C754-4D6F-BCE7-07F697BF0DDC@mattwynne.net> References: <21A6E676-C754-4D6F-BCE7-07F697BF0DDC@mattwynne.net> Message-ID: On Fri, Aug 29, 2008 at 7:25 AM, Matt Wynne wrote: > I have a goal to allow any of us on the team to be able to fetch the build > environment locally and run / hack it, them commit their changes back and be > able to easily deploy them to the team's shared build environment. Instead of moving where CRUISE_DATA_ROOT is, maybe you could just make a script which symlinks/copies the files you need from your project to the default location of ~/.cruise. For example, have a ./setup_ccrb.rb scrpt in your project which will clone the git repo, set up the project by issuing the correct .cruise add command, and symlink site_config.rb/css. You would have the same symlinks in the shared environment. All the symlinked files could live in the project - and there shouldn't be many more cruise-related files to symlink than site_config and css, right? -- Chad From jeremy.lightsmith at gmail.com Fri Aug 29 12:31:55 2008 From: jeremy.lightsmith at gmail.com (Jeremy Lightsmith) Date: Fri, 29 Aug 2008 09:31:55 -0700 Subject: [Cruisecontrolrb-users] Keeping CRUISE_DATA_ROUTE under version control In-Reply-To: References: <21A6E676-C754-4D6F-BCE7-07F697BF0DDC@mattwynne.net> Message-ID: <648eacf20808290931g747bf34ka1c4cdb2d96ccfa1@mail.gmail.com> the other file that you need is cruise_config.rb, this is a per project config file. in general, I'd suggest that it live inside the project itself, because it's much easier to configure that way. however, you can also place it in // and in fact there should be one there that cruise creates for you. why do you want to do what you're suggesting? I'm with chad, I think it'd be easier to create a script that recreates the cruise environment on a new machine and uses files that you have checked into your project. However, I don't know exactly what you're trying to do, maybe you have a good reason for doing it the way you're suggesting. Jeremy On Fri, Aug 29, 2008 at 8:13 AM, Chad Woolley wrote: > On Fri, Aug 29, 2008 at 7:25 AM, Matt Wynne wrote: > > I have a goal to allow any of us on the team to be able to fetch the > build > > environment locally and run / hack it, them commit their changes back and > be > > able to easily deploy them to the team's shared build environment. > > Instead of moving where CRUISE_DATA_ROOT is, maybe you could just make > a script which symlinks/copies the files you need from your project to > the default location of ~/.cruise. > > For example, have a ./setup_ccrb.rb scrpt in your project which will > clone the git repo, set up the project by issuing the correct .cruise > add command, and symlink site_config.rb/css. You would have the same > symlinks in the shared environment. All the symlinked files could > live in the project - and there shouldn't be many more cruise-related > files to symlink than site_config and css, right? > > -- Chad > _______________________________________________ > Cruisecontrolrb-users mailing list > Cruisecontrolrb-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: From matt at mattwynne.net Fri Aug 29 13:23:27 2008 From: matt at mattwynne.net (Matt Wynne) Date: Fri, 29 Aug 2008 18:23:27 +0100 Subject: [Cruisecontrolrb-users] Keeping CRUISE_DATA_ROUTE under version control In-Reply-To: <648eacf20808290931g747bf34ka1c4cdb2d96ccfa1@mail.gmail.com> References: <21A6E676-C754-4D6F-BCE7-07F697BF0DDC@mattwynne.net> <648eacf20808290931g747bf34ka1c4cdb2d96ccfa1@mail.gmail.com> Message-ID: On 29 Aug 2008, at 17:31, Jeremy Lightsmith wrote: > the other file that you need is cruise_config.rb, this is a per > project config file. in general, I'd suggest that it live inside > the project itself, because it's much easier to configure that > way. however, you can also place it in // > and in fact there should be one there that cruise creates for you. > > why do you want to do what you're suggesting? I'm with chad, I > think it'd be easier to create a script that recreates the cruise > environment on a new machine and uses files that you have checked > into your project. However, I don't know exactly what you're > trying to do, maybe you have a good reason for doing it the way > you're suggesting. > > Jeremy > Well basically I would like to be able to check-in and thus re-create the whole of our build environment (= ccrb app from github + our custom hacks thereto + project config) very easily from source control. This is for two reasons: - if we lose our server for some reason, it's trivial to recreate the build environment - people can easily clone the whole build environment and run it on their local dev machine, thereby reducing the friction of hacking and improving it I'm used to CC.Net where we had all those horrible XML files in source control, which was about the one thing from those days that made any sense. I take your and Chad's point about just checking in a script with the ./cruise add commands in it - I think that's what I'll do for now. I guess some day it might be worth considering extending SourceControl.detect etc to read cruise_config.rb and see if there are any source control settings in there (in precedence to looking in the work folder for .git, .svn etc). This would allow you to check in the cruise_config.rb files and thus check in your source control config. Does that make any more sense? cheers, Matt ---- http://blog.mattwynne.net http://songkick.com In case you wondered: The opinions expressed in this email are my own and do not necessarily reflect the views of any former, current or future employers of mine. > On Fri, Aug 29, 2008 at 8:13 AM, Chad Woolley > wrote: > On Fri, Aug 29, 2008 at 7:25 AM, Matt Wynne > wrote: > > I have a goal to allow any of us on the team to be able to fetch > the build > > environment locally and run / hack it, them commit their changes > back and be > > able to easily deploy them to the team's shared build environment. > > Instead of moving where CRUISE_DATA_ROOT is, maybe you could just make > a script which symlinks/copies the files you need from your project to > the default location of ~/.cruise. > > For example, have a ./setup_ccrb.rb scrpt in your project which will > clone the git repo, set up the project by issuing the correct .cruise > add command, and symlink site_config.rb/css. You would have the same > symlinks in the shared environment. All the symlinked files could > live in the project - and there shouldn't be many more cruise-related > files to symlink than site_config and css, right? > > -- Chad > _______________________________________________ > Cruisecontrolrb-users mailing list > Cruisecontrolrb-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users > > _______________________________________________ > Cruisecontrolrb-users mailing list > Cruisecontrolrb-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users -------------- next part -------------- An HTML attachment was scrubbed... URL: From jeremy.lightsmith at gmail.com Fri Aug 29 13:36:39 2008 From: jeremy.lightsmith at gmail.com (Jeremy Lightsmith) Date: Fri, 29 Aug 2008 10:36:39 -0700 Subject: [Cruisecontrolrb-users] Keeping CRUISE_DATA_ROUTE under version control In-Reply-To: References: <21A6E676-C754-4D6F-BCE7-07F697BF0DDC@mattwynne.net> <648eacf20808290931g747bf34ka1c4cdb2d96ccfa1@mail.gmail.com> Message-ID: <648eacf20808291036y5092effdjc40a9f324d8d6f5f@mail.gmail.com> not sure if I understand right. you currently can checkin your cruise_config.rb file right into the root directory of your project. this file can have any source control settings you want. the only problem is the chicken and egg problem that you need the cruise_config.rb to read the source control settings to download the project the first time. but if you put this into your script (that you check in), then I think you're golden. On Fri, Aug 29, 2008 at 10:23 AM, Matt Wynne wrote: > On 29 Aug 2008, at 17:31, Jeremy Lightsmith wrote: > > the other file that you need is cruise_config.rb, this is a per project > config file. in general, I'd suggest that it live inside the project > itself, because it's much easier to configure that way. however, you can > also place it in // and in fact there should be one > there that cruise creates for you. > > why do you want to do what you're suggesting? I'm with chad, I think it'd > be easier to create a script that recreates the cruise environment on a new > machine and uses files that you have checked into your project. However, I > don't know exactly what you're trying to do, maybe you have a good reason > for doing it the way you're suggesting. > > Jeremy > > > Well basically I would like to be able to check-in and thus re-create the > whole of our build environment (= ccrb app from github + our custom hacks > thereto + project config) very easily from source control. This is for two > reasons: - if we lose our server for some reason, it's trivial to recreate > the build environment > - people can easily clone the whole build environment and run it on their > local dev machine, thereby reducing the friction of hacking and improving it > > I'm used to CC.Net where we had all those horrible XML files in source > control, which was about the one thing from those days that made any sense. > > I take your and Chad's point about just checking in a script with the > ./cruise add commands in it - I think that's what I'll do for now. > > I guess some day it might be worth considering extending > SourceControl.detect etc to read cruise_config.rb and see if there are any > source control settings in there (in precedence to looking in the work > folder for .git, .svn etc). This would allow you to check in the > cruise_config.rb files and thus check in your source control config. > > Does that make any more sense? > > cheers, > Matt > ---- > http://blog.mattwynne.net > http://songkick.com > > In case you wondered: The opinions expressed in this email are my own and > do not necessarily reflect the views of any former, current or future > employers of mine. > > > On Fri, Aug 29, 2008 at 8:13 AM, Chad Woolley wrote: > >> On Fri, Aug 29, 2008 at 7:25 AM, Matt Wynne wrote: >> > I have a goal to allow any of us on the team to be able to fetch the >> build >> > environment locally and run / hack it, them commit their changes back >> and be >> > able to easily deploy them to the team's shared build environment. >> >> Instead of moving where CRUISE_DATA_ROOT is, maybe you could just make >> a script which symlinks/copies the files you need from your project to >> the default location of ~/.cruise. >> >> For example, have a ./setup_ccrb.rb scrpt in your project which will >> clone the git repo, set up the project by issuing the correct .cruise >> add command, and symlink site_config.rb/css. You would have the same >> symlinks in the shared environment. All the symlinked files could >> live in the project - and there shouldn't be many more cruise-related >> files to symlink than site_config and css, right? >> >> -- Chad >> _______________________________________________ >> Cruisecontrolrb-users mailing list >> Cruisecontrolrb-users at rubyforge.org >> http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users >> > > _______________________________________________ > Cruisecontrolrb-users mailing list > Cruisecontrolrb-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users > > > > _______________________________________________ > Cruisecontrolrb-users mailing list > Cruisecontrolrb-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From matt at mattwynne.net Sun Aug 31 13:37:06 2008 From: matt at mattwynne.net (Matt Wynne) Date: Sun, 31 Aug 2008 18:37:06 +0100 Subject: [Cruisecontrolrb-users] Keeping CRUISE_DATA_ROUTE under version control In-Reply-To: <648eacf20808291036y5092effdjc40a9f324d8d6f5f@mail.gmail.com> References: <21A6E676-C754-4D6F-BCE7-07F697BF0DDC@mattwynne.net> <648eacf20808290931g747bf34ka1c4cdb2d96ccfa1@mail.gmail.com> <648eacf20808291036y5092effdjc40a9f324d8d6f5f@mail.gmail.com> Message-ID: <5D55954E-D66F-4F13-8EB5-87F988608BE3@mattwynne.net> I guess what I want is for the chicken to come pre-packaged with enough information to be able to lay those eggs. I.e. my build server comes configured with the instructions it needs to fetch the various projects from source control and start building them. For example - for one rails project, I might want a build which runs every check-in and runs tests / specs, and another that runs nightly that runs selenium scripts etc. Pretty soon I'm going to end up with a bunch of hand-crafted stuff in /home/builder/.cruise on the build server which isn't backed up anywhere. I'm pretty new to linux, ruby and git, so there's a lot of stuff for me to absorb right now. Perhaps in a few weeks I'll be able to ask slightly more focussed questions! On 29 Aug 2008, at 18:36, Jeremy Lightsmith wrote: > not sure if I understand right. you currently can checkin your > cruise_config.rb file right into the root directory of your > project. this file can have any source control settings you want. > the only problem is the chicken and egg problem that you need the > cruise_config.rb to read the source control settings to download > the project the first time. but if you put this into your script > (that you check in), then I think you're golden. > > On Fri, Aug 29, 2008 at 10:23 AM, Matt Wynne > wrote: > On 29 Aug 2008, at 17:31, Jeremy Lightsmith wrote: > >> the other file that you need is cruise_config.rb, this is a per >> project config file. in general, I'd suggest that it live inside >> the project itself, because it's much easier to configure that >> way. however, you can also place it in // >> and in fact there should be one there that cruise creates for you. >> >> why do you want to do what you're suggesting? I'm with chad, I >> think it'd be easier to create a script that recreates the cruise >> environment on a new machine and uses files that you have checked >> into your project. However, I don't know exactly what you're >> trying to do, maybe you have a good reason for doing it the way >> you're suggesting. >> >> Jeremy >> > > Well basically I would like to be able to check-in and thus re- > create the whole of our build environment (= ccrb app from github + > our custom hacks thereto + project config) very easily from source > control. This is for two reasons: > - if we lose our server for some reason, it's trivial to recreate > the build environment > - people can easily clone the whole build environment and run it > on their local dev machine, thereby reducing the friction of > hacking and improving it > > I'm used to CC.Net where we had all those horrible XML files in > source control, which was about the one thing from those days that > made any sense. > > I take your and Chad's point about just checking in a script with > the ./cruise add commands in it - I think that's what I'll do for now. > > I guess some day it might be worth considering extending > SourceControl.detect etc to read cruise_config.rb and see if there > are any source control settings in there (in precedence to looking > in the work folder for .git, .svn etc). This would allow you to > check in the cruise_config.rb files and thus check in your source > control config. > > Does that make any more sense? > > cheers, > Matt > ---- > http://blog.mattwynne.net > http://songkick.com > > In case you wondered: The opinions expressed in this email are my > own and do not necessarily reflect the views of any former, current > or future employers of mine. > > >> On Fri, Aug 29, 2008 at 8:13 AM, Chad Woolley >> wrote: >> On Fri, Aug 29, 2008 at 7:25 AM, Matt Wynne >> wrote: >> > I have a goal to allow any of us on the team to be able to fetch >> the build >> > environment locally and run / hack it, them commit their changes >> back and be >> > able to easily deploy them to the team's shared build environment. >> >> Instead of moving where CRUISE_DATA_ROOT is, maybe you could just >> make >> a script which symlinks/copies the files you need from your >> project to >> the default location of ~/.cruise. >> >> For example, have a ./setup_ccrb.rb scrpt in your project which will >> clone the git repo, set up the project by issuing the correct .cruise >> add command, and symlink site_config.rb/css. You would have the same >> symlinks in the shared environment. All the symlinked files could >> live in the project - and there shouldn't be many more cruise-related >> files to symlink than site_config and css, right? >> >> -- Chad >> _______________________________________________ >> Cruisecontrolrb-users mailing list >> Cruisecontrolrb-users at rubyforge.org >> http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users >> >> _______________________________________________ >> Cruisecontrolrb-users mailing list >> Cruisecontrolrb-users at rubyforge.org >> http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users > > > _______________________________________________ > Cruisecontrolrb-users mailing list > Cruisecontrolrb-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users > > > _______________________________________________ > Cruisecontrolrb-users mailing list > Cruisecontrolrb-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users -------------- next part -------------- An HTML attachment was scrubbed... URL: