From thewoolleyman at gmail.com  Mon May 11 19:48:15 2009
From: thewoolleyman at gmail.com (Chad Woolley)
Date: Mon, 11 May 2009 16:48:15 -0700
Subject: [Cruisecontrolrb-developers] Sometimes 'git fetch origin' hangs
	builds
In-Reply-To: <e3af97510902270932j142f3b0ew80ade5edd8445d3b@mail.gmail.com>
References: <e3af97510902270932j142f3b0ew80ade5edd8445d3b@mail.gmail.com>
Message-ID: <e3af97510905111648q24860a9et4f21944b8a607f2b@mail.gmail.com>

On Fri, Feb 27, 2009 at 10:32 AM, Chad Woolley <thewoolleyman at gmail.com> wrote:
> I opened a ticket:
>
> http://cruisecontrolrb.lighthouseapp.com/projects/9150-cruise-control-rb/tickets/229-sometimes-git-hangs

We (Josh Susser and I) just committed a change which hopefully fixes
this error (we were unable to reproduce manually).  Let me know if
anyone still encounters builds hanging in git projects.

Thanks,
-- Chad

From gigix1980 at gmail.com  Wed May 20 05:25:26 2009
From: gigix1980 at gmail.com (Jeff Xiong)
Date: Wed, 20 May 2009 17:25:26 +0800
Subject: [Cruisecontrolrb-developers] Rails upgrade
In-Reply-To: <648eacf20905200203i911ca81veaffb22781064dc9@mail.gmail.com>
References: <OFE637C86A.5CA74523-ON862575BC.000D93C8-852575BC.000EC3CC@thoughtworks.com>
	<648eacf20905200203i911ca81veaffb22781064dc9@mail.gmail.com>
Message-ID: <20fd9dc50905200225x698f6275pc7c130beb956e9ad@mail.gmail.com>

Jeremy,

I'll check if there's nobody else handles this...

On Wed, May 20, 2009 at 5:03 PM, Jeremy Lightsmith
<jeremy.lightsmith at gmail.com> wrote:
> In general, it sounds great to me.
>
> My one concern is that we really, REALLY need to do a release.? I know
> Alexey was going to, but now that he's not at TW either, who has access to
> http://cruisecontrolrb.thoughtworks.com?? Does ccrb have a TW sponsor
> anymore?
>
> If we can muster some help to get the release out sooner than later, I'd
> hold off on the rails 2.3 upgrade until after that.? If we can't, then I'd
> go ahead and do it now.
>
> One thing to note, the current philosophy of ccrb is to make it dependency
> free.? So be sure when we upgrade to freeze the rails gems.
>
> Jeremy
>
> On Tue, May 19, 2009 at 7:41 PM, Brian Guthrie <bguthrie at thoughtworks.com>
> wrote:
>>
>> Hi all,
>>
>> A few of my colleagues and I have forked CCRB and have it running on Rails
>> 2.3. It doesn't fully integrate Rails 2 idioms yet, but it successfully
>> deploys on Passenger and builds itself. We've rebased with
>> thoughtworks/master as of a couple of hours ago. As a ThoughtWorker I have
>> access to the TW account on GitHub; would anyone object if we merged these
>> changes in? We'd be happy to integrate it as part of a distinct Rails 2
>> branch if need be.
>>
>> ?http://github.com/bguthrie/cruisecontrol.rb/tree/master
>>
>> Thanks all,
>>
>> Brian
>> _______________________________________________
>> Cruisecontrolrb-developers mailing list
>> Cruisecontrolrb-developers at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers
>>
>
>
>
> --
> Jeremy Lightsmith
> Coaching Teams & Creating Communities
>
> 312-953-1193
> http://onemanswalk.com/ (blog)
> http://facilitationpatterns.org/ (book in progress)
> http://www.linkedin.com/in/jeremylightsmith
>
> _______________________________________________
> Cruisecontrolrb-developers mailing list
> Cruisecontrolrb-developers at rubyforge.org
> http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers
>
>



-- 
Jeff Xiong
Software Journeyman - http://gigix.agilechina.net
Open Source Contributor - http://fluorida.googlecode.com/
Technical Evangelist - http://www.infoq.com/cn/

From thewoolleyman at gmail.com  Wed May 20 13:09:51 2009
From: thewoolleyman at gmail.com (Chad Woolley)
Date: Wed, 20 May 2009 10:09:51 -0700
Subject: [Cruisecontrolrb-developers] Rails upgrade
In-Reply-To: <OFA7B3891F.63552478-ON862575BC.0043A74D-852575BC.0043E414@thoughtworks.com>
References: <20fd9dc50905200225x698f6275pc7c130beb956e9ad@mail.gmail.com> 
	<OFA7B3891F.63552478-ON862575BC.0043A74D-852575BC.0043E414@thoughtworks.com>
Message-ID: <e3af97510905201009o1f8552e8ga23572c60fcdb374@mail.gmail.com>

On Wed, May 20, 2009 at 5:21 AM, Brian Guthrie
<bguthrie at thoughtworks.com> wrote:
>
> Alexey gave me his blessing to be the new maintainer before he left, but I
> haven't yet received the rubber-stamp from TW management and don't have
> access to the content on cruisecontrolrb.thoughtworks.com as of yet (nor do
> I have admin rights on the Lighthouse tracker).
> On Wed, May 20, 2009 at 5:03 PM, Jeremy Lightsmith
> <jeremy.lightsmith at gmail.com> wrote:
>> In general, it sounds great to me.
>>
>> My one concern is that we really, REALLY need to do a release.? I know
>> Alexey was going to, but now that he's not at TW either, who has access to
>> http://cruisecontrolrb.thoughtworks.com?? Does ccrb have a TW sponsor
>> anymore?

We depend heavily on CCRB at Pivotal Labs, and we have been
contributing bugfixes and patches, and I also spend my free time
monitoring this list and using CCRB for other projects (such as the
official Rails CI server).

Especially since Alexey left, the future of CCRB support from
ThoughtWorks is concerning to me.  Is ThoughtWorks committed to
maintaining CCRB long-term?  Is the release process still going to be
controlled only by ThoughtWorks?

For example - there's been several mentions of a badly-needed release
over the past few months, but nothing has happened.  I posted about
the broken official CCRB CI build/server (I think it is a Ruby 1.8.7
problem, and will try to fix eventually), but I got no responses on
that thread, and no apparent concern (I personally think it looks
pretty bad for the official build of a CI product to be red).

If CCRB is a strategic product for TW, and they want to maintain a
level of control, then I'd like to see official TW
representatives/sponsors responding more on this list, and driving
releases, patches, website updates, managing the official CI server,
etc.  I already have commit access and a signed TW NDA on file, so I'm
glad to help, but there's still many things I don't have permission to
do.

On the other hand, If TW is not going to take so much of an active
long-term involvement (perhaps because of focus on other CI products),
that is fine.  However, if this is the case, I'd like to see
everything open sourced and put under community ownership as well -
such as the website, official CI  server, release cycle, etc...

So, I'm not trying to be negative, but the current situation seems far
less than optimal, especially for a product my company and I depend on
heavily, and I'm wondering what will happen going forward.

Thanks,
-- Chad

From thewoolleyman at gmail.com  Fri May 22 16:52:26 2009
From: thewoolleyman at gmail.com (Chad Woolley)
Date: Fri, 22 May 2009 13:52:26 -0700
Subject: [Cruisecontrolrb-developers] Rails upgrade
In-Reply-To: <648eacf20905221339r2a871d59hfbb40cd3d4599141@mail.gmail.com>
References: <e3af97510905201009o1f8552e8ga23572c60fcdb374@mail.gmail.com> 
	<OF640A9D29.3B907475-ON862575BE.00590E9E-852575BE.005A1BAE@thoughtworks.com>
	<648eacf20905221339r2a871d59hfbb40cd3d4599141@mail.gmail.com>
Message-ID: <e3af97510905221352x57d30d0fh93810da862e9b2c@mail.gmail.com>

On Fri, May 22, 2009 at 1:39 PM, Jeremy Lightsmith
<jeremy.lightsmith at gmail.com> wrote:
> I also have been pretty
> impressed w/ integrity's simpleness.? I think it might be time to think
> about some changes.

It also is lacking many important features that CCRB has (svn support,
polling support, svn external/git submodule support, etc).  Yeah,
there may be some of these spread across various forks, but that
doesn't help me now.

It also seems very easy to get into dependency hell when
developing/using it.  Makes me appreciate CCRB's no-dependencies
approach.

CCRB does get a lot of things right, I think it just needs some update
love and new killer features.

-- Chad

From thewoolleyman at gmail.com  Fri May 22 18:30:55 2009
From: thewoolleyman at gmail.com (Chad Woolley)
Date: Fri, 22 May 2009 15:30:55 -0700
Subject: [Cruisecontrolrb-developers] Campfire notifier plugin?
Message-ID: <e3af97510905221530wc228ed6ob6e3ca6af286799@mail.gmail.com>

Anyone have one?

From donnoman at gmail.com  Sat May 30 22:00:18 2009
From: donnoman at gmail.com (Donovan Bray)
Date: Sat, 30 May 2009 19:00:18 -0700
Subject: [Cruisecontrolrb-developers] Adding a project description using the
	cruise_config.rb file.
Message-ID: <6657eb070905301900j65219c2occbc15299afdbc2f@mail.gmail.com>

I wanted to add a project description to each of my projects.

So I started with the projects cruise_config.rb

# Project-specific configuration for CruiseControl.rb

Project.configure do |project|
  project.description = "This is a project description"
end


I changed app/models/project.rb

-  attr_accessor :source_control, :scheduler
+  attr_accessor :source_control, :scheduler, :description

   def initialize(name, scm = nil)
     @name = name
+    @description = ''


I added the following to app/views/projects/_project.rhtml

   <td class="build_details">
+    <% if project.description %>
+      <p><%=project.description%></p>
+    <% end %>
     <% latest_build = recent_builds.first %>

I can force a description to show up in the view if I change
@description in the initialze method of project.rb to a value.

But the configuration value from cruise_config.rb never changes it.

What did I miss?