Nabble - CruiseControl.rb - Development

Re: Help with Git hanging bugs

2009-12-17T22:12:07Z

On Sun, Oct 4, 2009 at 11:16 PM, Chad Woolley <thewoolleyman@...> wrote:
> Matt Duncan has helped track this down, but the fix will involve the
> use of the SystemTimer native gem. I plan to use Bundler to manage
> this. Please see the ticket if you'd like to discuss:
>
> https://cruisecontrolrb.lighthouseapp.com/projects/9150-cruise-control-rb/tickets/229-sometimes-git-hangs#ticket-229-14

Fix committed in
http://github.com/thoughtworks/cruisecontrol.rb/commit/9309fc5fa7dab5a2ef1853e4295ce2d9f591f66d

system_timer gem will be used if it is installed.

I didn't do any auto-install or bundler stuff. KISS.

-- Chad
_______________________________________________
Cruisecontrolrb-developers mailing list
Cruisecontrolrb-developers@...
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers

Couple of bug fixes

2009-12-10T10:11:22Z

Hi all,

It's been quiet here for some time now :)

I just checked in a couple of changes., addressing the two biggest annoyances we had when using CC.rb @Scribd.

1. There is an interplay between builder cleaning old builds and dashboard listing builds that are being cleaned. Before these changes, it resulted in "phantom" unfinished builds for revisions that in fact were built days ago. This was caused by lazy initiation logic of the artefacts directory. Now, it's moved to constructor, is explicitly invoked when starting an actual new build, and life is good. Although you can still get an occasional HTTP500 from the dashboard (once in a couple of weeks) because of the same synchronization issue.

2. Even with 7 characters, Git revision numbers are not sufficiently unique. So, now CC.rb stores full revision guid in the file system, but displays only the first 7 characters thereof.

The next biggest annoyance for me is the API preformance. With 30 CCMenu's hitting it every second, lack of caching forced us to clear old builds often. Effectively, we only have build history for 3 days. Not a big deal, but meh. Same goes for the home page and RSS feed.

--
Alexey Verkhovsky
http://alex-verkhovsky.blogspot.com/
CruiseControl.rb [http://cruisecontrolrb.thoughtworks.com]

_______________________________________________
Cruisecontrolrb-developers mailing list
Cruisecontrolrb-developers@...
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers

Looking for some light cruise control help

2009-11-23T17:14:12Z

Need help cleaning up and documenting our cruisecontrol.rb deployment.

--
David Bristow djbristow@...

_______________________________________________
Cruisecontrolrb-developers mailing list
Cruisecontrolrb-developers@...
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers

Re: Making output limit configurable

2009-10-29T15:52:43Z

On Thu, Oct 29, 2009 at 1:11 PM, C. K. Ponnappa <ckponnappa@...> wrote:
> Folks,
>
> Shall I go ahead and merge Valentin's patch to make the output size
> configurable? You can find his changes at
> http://github.com/valo/cruisecontrol.rb

I'd feel better about it if the build were green and building reliably:

http://cruisecontrolrb.thoughtworks.com/builds/CruiseControlRB

-- Chad
_______________________________________________
Cruisecontrolrb-developers mailing list
Cruisecontrolrb-developers@...
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers

Making output limit configurable

2009-10-29T13:10:58Z

Folks,

Shall I go ahead and merge Valentin's patch to make the output size
configurable? You can find his changes at
http://github.com/valo/cruisecontrol.rb

Thanks,
Sidu.

-------- Original Message --------
Subject: Re: [GitHub] valo sent you a message
Date: Fri, 30 Oct 2009 01:37:50 +0530
From: C. K. Ponnappa <ckponnappa@...>
To: Valentin Mihov <valentin.mihov@...>
References: <4ae8b72d2e1e7_17ed3fe199347af04fc@...>
<4AE90456.3040005@...>
<45448450910290252h17a1c018ife55a1ffa194ca1b@...>

Sure Valentin, more tests are always welcome. In the meanwhile I will
get Alexey and others to review and once approved, I will merge changes.

Thanks ever so much!
Sidu.
http://blog.sidu.in
http://twitter.com/ponnappa

Valentin Mihov wrote:

> OK. This time the unit tests are not failing. I have forgotten to
> declare the assessors for the output_limit. I changed it in our CI,
> but forgot to push it to github. It should be better now.
>
> Should I write some unit tests for the new config var?
>
> Here is the fix:
> http://github.com/valo/cruisecontrol.rb/commit/e1037bff7278ba1471dd4b91b88ee8d86bb19f14
>
> Thanks,
> Valentin
>
> On Thu, Oct 29, 2009 at 4:56 AM, C. K. Ponnappa <ckponnappa@...> wrote:
>
>> Hey Valentin,
>>
>> Your patch looks good, but I have 7 failing tests after pulling; I just
>> wanted to confirm if this is happening for you (looks like a missing
>> cattr_reader :output_limit in Configuration)?
>> We can merge it in once the others have approved the change.
>>
>> Thanks,
>> Sidu.
>> http://blog.sidu.in
>> http://twitter.com/ponnappa
>>
>> GitHub wrote:
>>
>>> valo wants you to pull from valo/cruisecontrol.rb at master
>>>
>>> Body: Hi there!
>>>
>>> I made a patch to make the output limit of 100KB configurable. It is a
>>> global config option on the Configuration class. If you want and like the
>>> patch you can pull it.
>>>
>>> Please tell me if the fix is not good enough.
>>>
>>> Thanks,
>>> Valentin
>>>
>>> View repository: http://github.com/valo/cruisecontrol.rb/tree/master
>>>
>>>
>>>
>
>

_______________________________________________
Cruisecontrolrb-developers mailing list
Cruisecontrolrb-developers@...
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers

Re: [GitHub] valo sent you a message

2009-10-28T19:56:22Z

Hey Valentin,

Your patch looks good, but I have 7 failing tests after pulling; I just
wanted to confirm if this is happening for you (looks like a missing
cattr_reader :output_limit in Configuration)?
We can merge it in once the others have approved the change.

Thanks,
Sidu.
http://blog.sidu.in
http://twitter.com/ponnappa

GitHub wrote:

> valo wants you to pull from valo/cruisecontrol.rb at master
>
> Body: Hi there!
>
> I made a patch to make the output limit of 100KB configurable. It is a global config option on the Configuration class. If you want and like the patch you can pull it.
>
> Please tell me if the fix is not good enough.
>
> Thanks,
> Valentin
>
> View repository: http://github.com/valo/cruisecontrol.rb/tree/master
>
>

_______________________________________________
Cruisecontrolrb-developers mailing list
Cruisecontrolrb-developers@...
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers

Does Cruisecontrol build projects, that are developed in Ruby 1.8.7

2009-10-21T06:45:06Z

Hi,

I have project in Ruby as version 1.8.7. I am trying to use Crusiecontrol.rb to build the project. But, when I saw in the Cruisecontrol.rb documentation, in the prerequisite section, I found that, the Cruisecontrol is build in Ruby 1.8.6. It does not work on Ruby 1.8.7 or 1.8.9. As I told, I have developed the project in 1.8.7. I am doubt that,

Does the cruisecontrol works on my project to build?

Thank you

Re: (no subject)

2009-10-05T10:45:33Z

> BTW, I think LightHouse kinda sucks.

Uh-oh... I sense another ticket tracker migration in the wind :)

--Alex

On Mon, Oct 5, 2009 at 11:20 AM, Chad Woolley <thewoolleyman@...> wrote:

On Mon, Oct 5, 2009 at 9:59 AM, Alexey Verkhovsky
<alexey.verkhovsky@...> wrote:
> http://betarelease.github.com/2009/10/04/cruisecontrol-monitors-gotchas.html
>
> We should totally
>
> * make a saner alternative URL for the build status XML document (the .aspx
> thing harks back to when the only available dashboard monitor option was
> from CruiseControl.NET world).
> * display a rather prominent link to the aforesaid document from the /builds
> page. Probably also add an XML comment to it, explaining what it is.

Make a ticket in Lighthouse!

People have asked them for
months to allow emails notifications (such as this list) on new ticket
creation, and they still have not added it. Seems like they are just
letting it stagnate and not doing many new features.
_______________________________________________
Cruisecontrolrb-developers mailing list
Cruisecontrolrb-developers@...
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers

--
Alexey Verkhovsky
http://alex-verkhovsky.blogspot.com/
CruiseControl.rb [http://cruisecontrolrb.thoughtworks.com]

_______________________________________________
Cruisecontrolrb-developers mailing list
Cruisecontrolrb-developers@...
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers

Re: Help with Git hanging bugs

2009-10-05T10:43:57Z

On Mon, Oct 5, 2009 at 11:17 AM, Chad Woolley <thewoolleyman@...> wrote:

One note though - with Bundler, it doesn't install to a
global location, it is installed under vendor/gems

OK, that's much easier to swallow :) Sorry for making a bogus argument.

Maybe we can make the bundling automated, but only if there is an
"opt-in" flag in cruise config?

That doesn't make sense (not any better than ).

Or maybe do it on all supported
platforms unless there is an "opt-out" flag set?

I could probably live with that. With my "skeptical tester" hat on, I still expect bad things to happen though. See points (1), (2), (3), (4), (5) and - especially! - (6). By the time we address all those, it may well be so much effort that it doesn't make sense. Please, think about it.

Re: Help with Git hanging bugs

2009-10-05T10:32:53Z

As long as it isn't installing to a global location, my vote would be an opt-out for supported platforms. As it is now, the timeout config option is basically broken if a system call is what's hanging.

On Mon, Oct 5, 2009 at 1:17 PM, Chad Woolley <thewoolleyman@...> wrote:

On Mon, Oct 5, 2009 at 10:08 AM, Alexey Verkhovsky

<alexey.verkhovsky@...> wrote:

> (1) computers behind paranoid firewalls (by adding network timeout to every
> attempt to start an instance, which may or may not be infinite).
> (2) computers that don't have gcc or ruby-dev (increasing startup time)
> (3) you'll need to address what happens when several CC processes start from
> the same install at the same time (because, say, I like to run builder
> processes separately from the dashboard).
> (4) possibly, computers that run CC.rb under nologin accounts.
> (5) for people who don't want the system_timer gem for any reason
> whatsoever.
> (6) ???
>
> Seriously, a shrink-wrapped product should not silently install stuff into
> any global library locations, IMHO.

Good points. One note though - with Bundler, it doesn't install to a
global location, it is installed under vendor/gems. We can also do a
platform check, plus there is a 'placebo' stub gem on Windows.

Maybe we can make the bundling automated, but only if there is an
"opt-in" flag in cruise config? Or maybe do it on all supported
platforms unless there is an "opt-out" flag set?

_______________________________________________
Cruisecontrolrb-developers mailing list
Cruisecontrolrb-developers@...
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers

_______________________________________________
Cruisecontrolrb-developers mailing list
Cruisecontrolrb-developers@...
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers

Re: (no subject)

2009-10-05T10:20:41Z

On Mon, Oct 5, 2009 at 9:59 AM, Alexey Verkhovsky
<alexey.verkhovsky@...> wrote:
> http://betarelease.github.com/2009/10/04/cruisecontrol-monitors-gotchas.html
>
> We should totally
>
> * make a saner alternative URL for the build status XML document (the .aspx
> thing harks back to when the only available dashboard monitor option was
> from CruiseControl.NET world).
> * display a rather prominent link to the aforesaid document from the /builds
> page. Probably also add an XML comment to it, explaining what it is.

Make a ticket in Lighthouse!

BTW, I think LightHouse kinda sucks. People have asked them for
months to allow emails notifications (such as this list) on new ticket
creation, and they still have not added it. Seems like they are just
letting it stagnate and not doing many new features.
_______________________________________________
Cruisecontrolrb-developers mailing list
Cruisecontrolrb-developers@...
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers

Re: Help with Git hanging bugs

2009-10-05T10:17:48Z

On Mon, Oct 5, 2009 at 10:08 AM, Alexey Verkhovsky
<alexey.verkhovsky@...> wrote:

> (1) computers behind paranoid firewalls (by adding network timeout to every
> attempt to start an instance, which may or may not be infinite).
> (2) computers that don't have gcc or ruby-dev (increasing startup time)
> (3) you'll need to address what happens when several CC processes start from
> the same install at the same time (because, say, I like to run builder
> processes separately from the dashboard).
> (4) possibly, computers that run CC.rb under nologin accounts.
> (5) for people who don't want the system_timer gem for any reason
> whatsoever.
> (6) ???
>
> Seriously, a shrink-wrapped product should not silently install stuff into
> any global library locations, IMHO.

Good points. One note though - with Bundler, it doesn't install to a
global location, it is installed under vendor/gems. We can also do a
platform check, plus there is a 'placebo' stub gem on Windows.

Maybe we can make the bundling automated, but only if there is an
"opt-in" flag in cruise config? Or maybe do it on all supported
platforms unless there is an "opt-out" flag set?
_______________________________________________
Cruisecontrolrb-developers mailing list
Cruisecontrolrb-developers@...
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers

Re: Help with Git hanging bugs

2009-10-05T10:08:31Z

On Mon, Oct 5, 2009 at 10:53 AM, Chad Woolley <thewoolleyman@...> wrote:

We definitely can and should do that, but I'd still like to have a
fail-safe installation attempt

This would still suck on:

(1) computers behind paranoid firewalls (by adding network timeout to every attempt to start an instance, which may or may not be infinite).

(2) computers that don't have gcc or ruby-dev (increasing startup time)
(3) you'll need to address what happens when several CC processes start from the same install at the same time (because, say, I like to run builder processes separately from the dashboard).
(4) possibly, computers that run CC.rb under nologin accounts.
(5) for people who don't want the system_timer gem for any reason whatsoever.
(6) ???

Seriously, a shrink-wrapped product should not silently install stuff into any global library locations, IMHO.

--

Alexey Verkhovsky
http://alex-verkhovsky.blogspot.com/
CruiseControl.rb [http://cruisecontrolrb.thoughtworks.com]

_______________________________________________
Cruisecontrolrb-developers mailing list
Cruisecontrolrb-developers@...
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers

(no subject)

2009-10-05T09:59:47Z

http://betarelease.github.com/2009/10/04/cruisecontrol-monitors-gotchas.html

We should totally

* make a saner alternative URL for the build status XML document (the .aspx thing harks back to when the only available dashboard monitor option was from CruiseControl.NET world).
* display a rather prominent link to the aforesaid document from the /builds page. Probably also add an XML comment to it, explaining what it is.

--
Alexey Verkhovsky
http://alex-verkhovsky.blogspot.com/
CruiseControl.rb [http://cruisecontrolrb.thoughtworks.com]

_______________________________________________
Cruisecontrolrb-developers mailing list
Cruisecontrolrb-developers@...
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers

Re: Help with Git hanging bugs

2009-10-05T09:53:09Z

On Mon, Oct 5, 2009 at 9:03 AM, Alexey Verkhovsky
<alexey.verkhovsky@...> wrote:
> I don't like the sound of automaticaly installing native gems. This screams
> "maintenance nightmare" to me (think Windoze). Why don't we leave
> "SystemTimer not installed" as a fairly visible warning (written to the
> dashboard, and linked to a documentation page that explains the whole thing,
> perhaps)? This way, if a build gets stuck, people will easily find out why
> and take corrective action.

We definitely can and should do that, but I'd still like to have a
fail-safe installation attempt, just for my own selfish automation
purposes.
_______________________________________________
Cruisecontrolrb-developers mailing list
Cruisecontrolrb-developers@...
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers

Re: Help with Git hanging bugs

2009-10-05T09:03:05Z

All I can say is: ugh, timeout.rb rearing its ugly head again... :(

I don't like the sound of automaticaly installing native gems. This screams "maintenance nightmare" to me (think Windoze). Why don't we leave "SystemTimer not installed" as a fairly visible warning (written to the dashboard, and linked to a documentation page that explains the whole thing, perhaps)? This way, if a build gets stuck, people will easily find out why and take corrective action.

--Alex

On Mon, Oct 5, 2009 at 12:16 AM, Chad Woolley <thewoolleyman@...> wrote:

Matt Duncan has helped track this down, but the fix will involve the
use of the SystemTimer native gem. I plan to use Bundler to manage
this. Please see the ticket if you'd like to discuss:

_______________________________________________
Cruisecontrolrb-developers mailing list
Cruisecontrolrb-developers@...
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers

Re: Help with Git hanging bugs

2009-10-04T23:16:10Z

On Tue, Jul 28, 2009 at 6:35 PM, Chad Woolley <thewoolleyman@...> wrote:
> We've taken a shot at fixing this with a timeout loop, but it still
> happens sometimes. It only happens in certain scenarios, and is
> hard (impossible for me so far) to reproduce. I've recorded the info
> I have in the comments of the ticket. Any help or further info is
> welcome:
>
> https://cruisecontrolrb.lighthouseapp.com/projects/9150/tickets/229-sometimes-git-hangs

Matt Duncan has helped track this down, but the fix will involve the
use of the SystemTimer native gem. I plan to use Bundler to manage
this. Please see the ticket if you'd like to discuss:

https://cruisecontrolrb.lighthouseapp.com/projects/9150-cruise-control-rb/tickets/229-sometimes-git-hangs#ticket-229-14

-- Chad
_______________________________________________
Cruisecontrolrb-developers mailing list
Cruisecontrolrb-developers@...
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers

Re: A bug introduced by Rails upgrade

2009-09-29T21:18:10Z

already fixed.

On Tue, Sep 29, 2009 at 7:28 PM, Chad Woolley <thewoolleyman@...> wrote:

On Tue, Sep 29, 2009 at 5:27 PM, Alexey Verkhovsky
<alexey.verkhovsky@...> wrote:
> This code in BuildsController#artifact:
>
> redirect_to :path => (params[:path] + '/index.html')
>
> now redirects to something like
> http://ci.scribd.com/builds/scribd-rcov/9f93094/coverage%2Findex.html
>
> Note the URI-escaped slash character before index.html. I'm pretty certain
> it wasn't happening at some earlier time.
> Relevant routes.rb entry:
> map.build_artifact 'builds/:project/:build/*path', :controller =>
> 'builds', :action => 'artifact', :build => /[^\/]+/
>
> Not sure how to fix this yet. Any suggestions?

Is it the regexp in the route? Maybe remove that and have a
controller action to do the same logic and redirect? Or else figure
out why the regexp is breaking?
_______________________________________________
Cruisecontrolrb-developers mailing list
Cruisecontrolrb-developers@...
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers

Re: A bug introduced by Rails upgrade

2009-09-29T18:28:08Z

On Tue, Sep 29, 2009 at 5:27 PM, Alexey Verkhovsky
<alexey.verkhovsky@...> wrote:

> This code in BuildsController#artifact:
>
> redirect_to :path => (params[:path] + '/index.html')
>
> now redirects to something like
> http://ci.scribd.com/builds/scribd-rcov/9f93094/coverage%2Findex.html
>
> Note the URI-escaped slash character before index.html. I'm pretty certain
> it wasn't happening at some earlier time.
> Relevant routes.rb entry:
> map.build_artifact 'builds/:project/:build/*path', :controller =>
> 'builds', :action => 'artifact', :build => /[^\/]+/
>
> Not sure how to fix this yet. Any suggestions?

Is it the regexp in the route? Maybe remove that and have a
controller action to do the same logic and redirect? Or else figure
out why the regexp is breaking?
_______________________________________________
Cruisecontrolrb-developers mailing list
Cruisecontrolrb-developers@...
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers

A bug introduced by Rails upgrade

2009-09-29T17:27:14Z

This code in BuildsController#artifact:

redirect_to :path => (params[:path] + '/index.html')

now redirects to something like http://ci.scribd.com/builds/scribd-rcov/9f93094/coverage%2Findex.html

Note the URI-escaped slash character before index.html. I'm pretty certain it wasn't happening at some earlier time.
Relevant routes.rb entry:
map.build_artifact 'builds/:project/:build/*path', :controller => 'builds', :action => 'artifact', :build => /[^\/]+/

Not sure how to fix this yet. Any suggestions?

--
Alexey Verkhovsky
http://alex-verkhovsky.blogspot.com/
CruiseControl.rb [http://cruisecontrolrb.thoughtworks.com]

_______________________________________________
Cruisecontrolrb-developers mailing list
Cruisecontrolrb-developers@...
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers

ccrb and mod_passenger(aka mod_rails)

2009-09-23T07:53:23Z

Before I look into it I figured I should ask first to potentially save some
wasted efford. Has anyone attempted and/or succeeded in installing ccrb
under mod_passenger on apache?

Thanks,
-Craig
_______________________________________________
Cruisecontrolrb-developers mailing list
Cruisecontrolrb-developers@...
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers

Re: Nightly builds

2009-09-22T18:22:36Z

We wrote a ScheduledBuildTrigger to accomplish this on a previous
project and I've been meaning to integrate it but rolled off and lost
access to the source code. As soon as I can get my hands on it I'll
plan on merging it in, but it's my understanding that there's no
builtin facility for this right now.

Brian

On Tue, Sep 22, 2009 at 5:11 PM, Chad Woolley <thewoolleyman@...> wrote:

> On Tue, Sep 22, 2009 at 4:08 PM, Alexey Verkhovsky
> <alexey.verkhovsky@...> wrote:
>> All,
>>
>> A stupid question: how in the current scheme of things would you go about
>> creating a nightly build (something that runs at a certain time every day,
>> no matter what)? I can only think of a daily cron that does "touch
>> ~/.cruise/projects/foo/build_requested". Which is kind of a meh, because
>> it's a piece of configuration unduly separated from cruise_config.rb
>>
>> I'm thinking of the following addition to the config language:
>>
>> project.build_every :hour, :at => 15.minutes # default 0.minutes, so every
>> hour on the hour
>> project.build_every :day, :at => "01:00:00" # default 01:00:00
>> project.build_every :week, :on => "Wed", :at => "01:00:00" # default
>> Monday, 01:00:00
>>
>> Would this be a desirable feature or a kitchen sink?
>
> People ask for this all the time, and I always assumed it was possible
> without investigating. It isn't? Or is it only possible to build at
> a given interval, but not at a given time?
>
> In any case, I think the language you propose would be a good addition.
>
> -- Chad
> _______________________________________________
> Cruisecontrolrb-developers mailing list
> Cruisecontrolrb-developers@...
> http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers
>

_______________________________________________
Cruisecontrolrb-developers mailing list
Cruisecontrolrb-developers@...
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers

Re: Nightly builds

2009-09-22T17:11:38Z

On Tue, Sep 22, 2009 at 4:08 PM, Alexey Verkhovsky
<alexey.verkhovsky@...> wrote:

> All,
>
> A stupid question: how in the current scheme of things would you go about
> creating a nightly build (something that runs at a certain time every day,
> no matter what)? I can only think of a daily cron that does "touch
> ~/.cruise/projects/foo/build_requested". Which is kind of a meh, because
> it's a piece of configuration unduly separated from cruise_config.rb
>
> I'm thinking of the following addition to the config language:
>
> project.build_every :hour, :at => 15.minutes # default 0.minutes, so every
> hour on the hour
> project.build_every :day, :at => "01:00:00" # default 01:00:00
> project.build_every :week, :on => "Wed", :at => "01:00:00" # default
> Monday, 01:00:00
>
> Would this be a desirable feature or a kitchen sink?

People ask for this all the time, and I always assumed it was possible
without investigating. It isn't? Or is it only possible to build at
a given interval, but not at a given time?

In any case, I think the language you propose would be a good addition.

-- Chad
_______________________________________________
Cruisecontrolrb-developers mailing list
Cruisecontrolrb-developers@...
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers

Nightly builds

2009-09-22T16:08:32Z

All,

A stupid question: how in the current scheme of things would you go about creating a nightly build (something that runs at a certain time every day, no matter what)? I can only think of a daily cron that does "touch ~/.cruise/projects/foo/build_requested". Which is kind of a meh, because it's a piece of configuration unduly separated from cruise_config.rb

I'm thinking of the following addition to the config language:

project.build_every :hour, :at => 15.minutes # default 0.minutes, so every hour on the hour
project.build_every :day, :at => "01:00:00" # default 01:00:00
project.build_every :week, :on => "Wed", :at => "01:00:00" # default Monday, 01:00:00

Would this be a desirable feature or a kitchen sink?

--
Alexey Verkhovsky
http://alex-verkhovsky.blogspot.com/
CruiseControl.rb [http://cruisecontrolrb.thoughtworks.com]

_______________________________________________
Cruisecontrolrb-developers mailing list
Cruisecontrolrb-developers@...
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers

Re: CCRB CI build has been hung for a couple months and test suite is broken

2009-09-22T09:05:26Z

On Mon, Sep 21, 2009 at 9:21 PM, Alexey Verkhovsky
<alexey.verkhovsky@...> wrote:
> On Mon, Sep 21, 2009 at 8:59 PM, Chad Woolley <thewoolleyman@...>
> wrote:
>>
>> Integration tests are still broken, though...
>
> It all passes for me - and I have no ~/.cruise directory on this laptop.

Did you specifically run rake test:integration? They don't run as
part of the suite anymore...
_______________________________________________
Cruisecontrolrb-developers mailing list
Cruisecontrolrb-developers@...
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers

Re: Need another plugin event (build_still_broken) - and yeah, I'm using CC.rb again

2009-09-21T21:22:25Z

On Mon, Sep 21, 2009 at 8:36 PM, Chad Woolley <thewoolleyman@...> wrote:

> Unless someone has a better name for it. Any takers?

"yet_another_broken_build"?

Smilies, please! :) It's almost 9:30 pm, jokes are getting harder to filter.

--
Alexey Verkhovsky
http://alex-verkhovsky.blogspot.com/
CruiseControl.rb [http://cruisecontrolrb.thoughtworks.com]

_______________________________________________
Cruisecontrolrb-developers mailing list
Cruisecontrolrb-developers@...
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers

Re: CCRB CI build has been hung for a couple months and test suite is broken

2009-09-21T21:21:06Z

On Mon, Sep 21, 2009 at 8:59 PM, Chad Woolley <thewoolleyman@...> wrote:

Integration tests are still broken, though...

It all passes for me - and I have no ~/.cruise directory on this laptop.

--
Alexey Verkhovsky
http://alex-verkhovsky.blogspot.com/
CruiseControl.rb [http://cruisecontrolrb.thoughtworks.com]

_______________________________________________
Cruisecontrolrb-developers mailing list
Cruisecontrolrb-developers@...
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers

Re: CCRB CI build has been hung for a couple months and test suite is broken

2009-09-21T20:59:00Z

On Sun, Sep 20, 2009 at 7:44 PM, Chad Woolley <thewoolleyman@...> wrote:
> I still see several non-integration failures, such as project_test.rb.

I tracked this down. I had to set RAILS_ENV=test at top of
test_helper.rb (this is the default for rails 2.3.2). It was
defaulting to development, and causing spurious test failures by
picking up settings from local ~/.cruise.

Integration tests are still broken, though...
_______________________________________________
Cruisecontrolrb-developers mailing list
Cruisecontrolrb-developers@...
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers

Re: Need another plugin event (build_still_broken) - and yeah, I'm using CC.rb again

2009-09-21T20:36:56Z

On Mon, Sep 21, 2009 at 6:54 PM, Alexey Verkhovsky
<alexey.verkhovsky@...> wrote:
> 2 minutes ago, I was somewhat surprised to discover that there is no good
> way for a plugin to distinguish between "build broken" (failure after a
> successful build) and "build still broken" (all subsequent consecutive
> failures) events. So, I want to add a plugin event "build_still_broken".
> Unless someone has a better name for it. Any takers?

"yet_another_broken_build"?
_______________________________________________
Cruisecontrolrb-developers mailing list
Cruisecontrolrb-developers@...
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers

Need another plugin event (build_still_broken) - and yeah, I'm using CC.rb again

2009-09-21T18:54:17Z

Hi, all,

2 minutes ago, I was somewhat surprised to discover that there is no good way for a plugin to distinguish between "build broken" (failure after a successful build) and "build still broken" (all subsequent consecutive failures) events. So, I want to add a plugin event "build_still_broken". Unless someone has a better name for it. Any takers?

And - yes - I'm a happy (in light of the aforesaid, almost happy) CC.rb user again :)

--
Alexey Verkhovsky
http://alex-verkhovsky.blogspot.com/
CruiseControl.rb [http://cruisecontrolrb.thoughtworks.com]

_______________________________________________
Cruisecontrolrb-developers mailing list
Cruisecontrolrb-developers@...
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers

Re: CCRB CI build has been hung for a couple months and test suite is broken

2009-09-21T08:51:56Z

I had failures even after your patches. We can discuss offline.

On Monday, September 21, 2009, Matt Duncan <mrduncan@...> wrote:

> I haven't had a chance to double-check but the patches that Chad cherry-picked from my fork and pushed should have all of the functional, unit, and integration tests passing on ruby 1.8.6, 1.8.7, and 1.9.1 (probably 1.9.2 also) now. Please let me know if anyone is encountering issues.
>
> On Sun, Sep 20, 2009 at 10:44 PM, Chad Woolley <thewoolleyman@... <javascript:_e({}, 'cvml', 'thewoolleyman@...');>> wrote:
>
>
> On Fri, Sep 18, 2009 at 2:58 PM, Brian Guthrie <btguthrie@... <javascript:_e({}, 'cvml', 'btguthrie@...');>> wrote:
>> Never mind, I spoke too soon. A couple of the builder integration
>> tests are still having issues. I'll ping the list again when I know
>> more.
>
> I still see several non-integration failures, such as project_test.rb.
> Any ETA on getting things green again? Do you need help? I'm about
> to apply some contributed patches, and I feel like I'm working without
> Annette. I sure miss her when she's gone...
>
> -- Chad
> _______________________________________________
> Cruisecontrolrb-developers mailing list
> Cruisecontrolrb-developers@...
> http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers
>
>

_______________________________________________
Cruisecontrolrb-developers mailing list
Cruisecontrolrb-developers@...
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers

Re: CCRB CI build has been hung for a couple months and test suite is broken

2009-09-21T05:00:14Z

I haven't had a chance to double-check but the patches that Chad cherry-picked from my fork and pushed should have all of the functional, unit, and integration tests passing on ruby 1.8.6, 1.8.7, and 1.9.1 (probably 1.9.2 also) now. Please let me know if anyone is encountering issues.

On Sun, Sep 20, 2009 at 10:44 PM, Chad Woolley <thewoolleyman@...> wrote:

On Fri, Sep 18, 2009 at 2:58 PM, Brian Guthrie <btguthrie@...> wrote:
> Never mind, I spoke too soon. A couple of the builder integration
> tests are still having issues. I'll ping the list again when I know
> more.

I still see several non-integration failures, such as project_test.rb.
Any ETA on getting things green again? Do you need help? I'm about
to apply some contributed patches, and I feel like I'm working without
Annette. I sure miss her when she's gone...

-- Chad
_______________________________________________
Cruisecontrolrb-developers mailing list
Cruisecontrolrb-developers@...
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers

_______________________________________________
Cruisecontrolrb-developers mailing list
Cruisecontrolrb-developers@...
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers

Re: CCRB CI build has been hung for a couple months and test suite is broken

2009-09-20T19:44:58Z

On Fri, Sep 18, 2009 at 2:58 PM, Brian Guthrie <btguthrie@...> wrote:
> Never mind, I spoke too soon. A couple of the builder integration
> tests are still having issues. I'll ping the list again when I know
> more.

I still see several non-integration failures, such as project_test.rb.
Any ETA on getting things green again? Do you need help? I'm about
to apply some contributed patches, and I feel like I'm working without
Annette. I sure miss her when she's gone...

-- Chad
_______________________________________________
Cruisecontrolrb-developers mailing list
Cruisecontrolrb-developers@...
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers

Re: CCRB CI build has been hung for a couple months and test suite is broken

2009-09-18T14:58:13Z

Never mind, I spoke too soon. A couple of the builder integration
tests are still having issues. I'll ping the list again when I know
more.

Brian

On Fri, Sep 18, 2009 at 5:55 PM, Brian Guthrie <btguthrie@...> wrote:

> All tests are passing both individually and together for me now but
> the cruisecontrolrb server still needs to be given a bit of a kick.
> Please pull and let me know if you encounter any issues.
>
> Brian
>
> On Tue, Sep 8, 2009 at 10:27 AM, Brian Guthrie <btguthrie@...> wrote:
>> Ticket updated with comments. It's a weird way of loading plugins and
>> I'm not surprised it's causing issues but I am surprised it was that
>> change wut done it. Problem-solving skills engaged.
>>
>> Brian
>>
>> On Mon, Sep 7, 2009 at 2:57 PM, Chad Woolley<thewoolleyman@...> wrote:
>>> On Wed, Sep 2, 2009 at 9:19 PM, C. K. Ponnappa <ckponnappa@...> wrote:
>>>> Hey Chad, apologies for the radio silence. I will take a look at this over
>>>> the weekend.
>>>
>>> Please take a look at this comment (and it would be great to get some
>>> input from some of the other original CCRB authors):
>>>
>>> https://cruisecontrolrb.lighthouseapp.com/projects/9150-cruise-control-rb/tickets/271-test-suite-broken-in-various-ways#ticket-271-5
>>>
>>> Thanks,
>>> -- Chad
>>> _______________________________________________
>>> Cruisecontrolrb-developers mailing list
>>> Cruisecontrolrb-developers@...
>>> http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers
>>>
>>
>

_______________________________________________
Cruisecontrolrb-developers mailing list
Cruisecontrolrb-developers@...
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers

Re: CCRB CI build has been hung for a couple months and test suite is broken

2009-09-18T14:55:35Z

All tests are passing both individually and together for me now but
the cruisecontrolrb server still needs to be given a bit of a kick.
Please pull and let me know if you encounter any issues.

Brian

On Tue, Sep 8, 2009 at 10:27 AM, Brian Guthrie <btguthrie@...> wrote:

> Ticket updated with comments. It's a weird way of loading plugins and
> I'm not surprised it's causing issues but I am surprised it was that
> change wut done it. Problem-solving skills engaged.
>
> Brian
>
> On Mon, Sep 7, 2009 at 2:57 PM, Chad Woolley<thewoolleyman@...> wrote:
>> On Wed, Sep 2, 2009 at 9:19 PM, C. K. Ponnappa <ckponnappa@...> wrote:
>>> Hey Chad, apologies for the radio silence. I will take a look at this over
>>> the weekend.
>>
>> Please take a look at this comment (and it would be great to get some
>> input from some of the other original CCRB authors):
>>
>> https://cruisecontrolrb.lighthouseapp.com/projects/9150-cruise-control-rb/tickets/271-test-suite-broken-in-various-ways#ticket-271-5
>>
>> Thanks,
>> -- Chad
>> _______________________________________________
>> Cruisecontrolrb-developers mailing list
>> Cruisecontrolrb-developers@...
>> http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers
>>
>

_______________________________________________
Cruisecontrolrb-developers mailing list
Cruisecontrolrb-developers@...
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers