David Heinemeier Hansson wrote:
I think just emailing this list on breakage is good. Then anyone has a
chance to help fix the bug. If it becomes too spammy, we'll make a
separate list for it.
Thanks for doing this! Now someone working with MS SQL, DB2, and all
the other non-oss adapters please f
> Thanks. I expect to get some form of the automated testing done today,
> with alerts just going to me for right now until I confirm it's working
> properly. My goal is to get it to test each specific revision, so it'll
> know which checkin broke, and email the details to both me, and with
> permi
David Heinemeier Hansson wrote:
I'm about set to automate the Oracle unit tests, but need to get the
green light lit first. Just submitted a patch to clean up the few
remaining issues...
http://dev.rubyonrails.org/ticket/4573
Applied.
Thanks. I expect to get some form of the automate
> I'm about set to automate the Oracle unit tests, but need to get the
> green light lit first. Just submitted a patch to clean up the few
> remaining issues...
>
> http://dev.rubyonrails.org/ticket/4573
Applied.
--
David Heinemeier Hansson
http://www.loudthinking.com -- Broadcasting Brain
David Heinemeier Hansson wrote:
You could have another list with a Reply-To this list and when the build breaks,
additionally cc the committer that broke the build.
I'd love to see that happen. Please Do Investigate.
I'm about set to automate the Oracle unit tests, but need to get the
gree
* Steve Longdo ([EMAIL PROTECTED]) [060331 15:21]:
> good stuff!
>
> http://en.wikipedia.org/wiki/Continuous_integration
>
> http://docs.codehaus.org/display/DAMAGECONTROL/
> Continuous+Integration+Server+Feature+Matrix
We've found the simple continuous_builder plugin for rails to be qui
Smells a bit like something that's been cooking in the Rails Recipes kitchen.-Derrick SpellOn Mar 31, 2006, at 3:10 PM, Steve Longdo wrote:good stuff!http://en.wikipedia.org/wiki/Continuous_integration http://docs.codehaus.org/display/DAMAGECONTROL/Continuous+Integration+Server+Feature+Matr
good stuff!http://en.wikipedia.org/wiki/Continuous_integration
http://docs.codehaus.org/display/DAMAGECONTROL/Continuous+Integration+Server+Feature+Matrix-SteveOn 3/31/06, Michael Schoen <
[EMAIL PROTECTED]> wrote:Blair Zajac wrote:> You could have another list with a Reply-To this list and
Blair Zajac wrote:
You could have another list with a Reply-To this list and when the build
breaks, additionally cc the committer that broke the build.
Seems like that might require running the test after each individual
commit, in order to be certain which commit break the build.
__
> You could have another list with a Reply-To this list and when the build
> breaks,
> additionally cc the committer that broke the build.
I'd love to see that happen. Please Do Investigate.
--
David Heinemeier Hansson
http://www.loudthinking.com -- Broadcasting Brain
http://www.basecamphq.com
David Heinemeier Hansson wrote:
What do you have in mind?
I could put something together to pull down edge rails every few hours,
run `rake test_oracle` and email on failures.
I think that would be great. If we could make it low-noise enough, we
could even just have it email this list. Or we
> What do you have in mind?
>
> I could put something together to pull down edge rails every few hours,
> run `rake test_oracle` and email on failures.
I think that would be great. If we could make it low-noise enough, we
could even just have it email this list. Or we could setup a
rails-test list
David Heinemeier Hansson wrote:
This is a good reason why it would be awesome to setup automated
testing for all the db adapters.
What do you have in mind?
I could put something together to pull down edge rails every few hours,
run `rake test_oracle` and email on failures.
Though that would
> A docs cleanup right before the 1.1 release broke ActiveRecord for
> anyone that has Ruby-OCI8 installed, even if they're not actually using it.
I broke it. Applied the patch. We'll probably do a 1.1.1 in a little
week's time. When we've had a chance to see what else shakes out of
this upgrade.
A docs cleanup right before the 1.1 release broke ActiveRecord for
anyone that has Ruby-OCI8 installed, even if they're not actually using it.
There have been at least a dozen or so messages on the general rails
list in the past few days about this problem, as it just completely
breaks Rails.
15 matches
Mail list logo