rake migrate fails, questions about trigging build

[Dan Reading]

Yesterday I installed a new (from scratch) instance of DC and played
with it for a while.

Q: How do I manually kick off a build?
Q: Using Subversion how do I trigger a build from post-commit script?
(sorry I don't seem to see any documentation for the developers
version of DamageControl.)

Today I started over again with fresh checkout but 'rake migrate'
fails:

damagecontrol@buildit:~/DC$ svn up

Fetching external item into 'vendor/rails'
External at revision 3253.

At revision 1724.
damagecontrol@buildit:~/DC$ rake migrate --trace
(in /scm/damagecontrol/DC)
** Invoke migrate (first_time)
** Invoke environment (first_time)
** Execute environment
** Execute migrate
rake aborted!
could not open database
/usr/lib/ruby/gems/1.8/gems/sqlite3-ruby-1.1.0/lib/sqlite3/errors.rb:94:in `check'
/usr/lib/ruby/gems/1.8/gems/sqlite3-ruby-1.1.0/lib/sqlite3/database.rb:112:in `initialize'
./vendor/rails/activerecord/lib/active_record/connection_adapters/sqlite_adapter.rb:17:in `sqlite3_connection'
./vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/connection_specification.rb:146:in `connection_without_query_cache='
./vendor/rails/activerecord/lib/active_record/query_cache.rb:54:in `connection='
./vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/connection_specification.rb:107:in `retrieve_connection'
./vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/connection_specification.rb:20:in `connection'
./vendor/rails/activerecord/lib/active_record/migration.rb:178:in `migrate'
./vendor/rails/railties/lib/tasks/databases.rake:3
/usr/lib/ruby/gems/1.8/gems/rake-0.6.2/lib/rake.rb:202:in `execute'
/usr/lib/ruby/gems/1.8/gems/rake-0.6.2/lib/rake.rb:202:in `execute'
/usr/lib/ruby/gems/1.8/gems/rake-0.6.2/lib/rake.rb:180:in `invoke'
/usr/lib/ruby/gems/1.8/gems/rake-0.6.2/lib/rake.rb:1454:in `run'
/usr/lib/ruby/gems/1.8/gems/rake-0.6.2/lib/rake.rb:1454:in `run'
/usr/lib/ruby/gems/1.8/gems/rake-0.6.2/bin/rake:7
/usr/bin/rake:18
damagecontrol@buildit:~/DC$


-- Dan R.
reading@...

[Aslak Hellesoy]

On 12/8/05, Dan Reading <reading@...> wrote:
>
> Yesterday I installed a new (from scratch) instance of DC and played
> with it for a while.
>
> Q: How do I manually kick off a build?

In the web interface, click on the revision you want to build. It
should expand and display a link that says "Trigger build for this
revision".

> Q: Using Subversion how do I trigger a build from post-commit script?
> (sorry I don't seem to see any documentation for the developers
> version of DamageControl.)
>

This is not in place yet. The way it is going to work is to have
post-commit invoke curl, which will issue a HTTP POST to DC. DC will
then trigger a build.

Should be pretty easy to add - just haven't gotten around to it yet.

> Today I started over again with fresh checkout but 'rake migrate'
> fails:
>
> damagecontrol@buildit:~/DC$ svn up
>
> Fetching external item into 'vendor/rails'
> External at revision 3253.
>
> At revision 1724.
> damagecontrol@buildit:~/DC$ rake migrate --trace
> (in /scm/damagecontrol/DC)
> ** Invoke migrate (first_time)
> ** Invoke environment (first_time)
> ** Execute environment
> ** Execute migrate
> rake aborted!
> could not open database
> /usr/lib/ruby/gems/1.8/gems/sqlite3-ruby-1.1.0/lib/sqlite3/errors.rb:94:in `check'
> /usr/lib/ruby/gems/1.8/gems/sqlite3-ruby-1.1.0/lib/sqlite3/database.rb:112:in `initialize'
> ./vendor/rails/activerecord/lib/active_record/connection_adapters/sqlite_adapter.rb:17:in `sqlite3_connection'
>

Seems like a SQLite concurrency issue
(http://www.google.com/search?q=sqlite3/errors.rb%3A94). Try to stop
DC and run migrations again.

HTH,
Aslak


./vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/connection_specification.rb:146:in
`connection_without_query_cache='

> ./vendor/rails/activerecord/lib/active_record/query_cache.rb:54:in `connection='
> ./vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/connection_specification.rb:107:in `retrieve_connection'
> ./vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/connection_specification.rb:20:in `connection'
> ./vendor/rails/activerecord/lib/active_record/migration.rb:178:in `migrate'
> ./vendor/rails/railties/lib/tasks/databases.rake:3
> /usr/lib/ruby/gems/1.8/gems/rake-0.6.2/lib/rake.rb:202:in `execute'
> /usr/lib/ruby/gems/1.8/gems/rake-0.6.2/lib/rake.rb:202:in `execute'
> /usr/lib/ruby/gems/1.8/gems/rake-0.6.2/lib/rake.rb:180:in `invoke'
> /usr/lib/ruby/gems/1.8/gems/rake-0.6.2/lib/rake.rb:1454:in `run'
> /usr/lib/ruby/gems/1.8/gems/rake-0.6.2/lib/rake.rb:1454:in `run'
> /usr/lib/ruby/gems/1.8/gems/rake-0.6.2/bin/rake:7
> /usr/bin/rake:18
> damagecontrol@buildit:~/DC$
>
>
> -- Dan R.
> reading@...
>

[Aslak Hellesoy]

> > rake aborted!
> > could not open database
> > /usr/lib/ruby/gems/1.8/gems/sqlite3-ruby-1.1.0/lib/sqlite3/errors.rb:94:in `check'
> > /usr/lib/ruby/gems/1.8/gems/sqlite3-ruby-1.1.0/lib/sqlite3/database.rb:112:in `initialize'
> > ./vendor/rails/activerecord/lib/active_record/connection_adapters/sqlite_adapter.rb:17:in `sqlite3_connection'
> >
>
> Seems like a SQLite concurrency issue
> (http://www.google.com/search?q=sqlite3/errors.rb%3A94). Try to stop
> DC and run migrations again.
>

I ran into the same issue myself. It seems to be a RoR regression
introduced here:
http://dev.rubyonrails.org/changeset/3244

I have reopened the associated ticket with a new patch:
http://dev.rubyonrails.org/ticket/3116

Aslak

[Robert Smallshire]

Hi folks,

I've been following this project for around 18 months on both the
Development and Users mailing lists. I've always though DamageControl
promised to be exactly the tool I was after.

Much as I hesitate to criticise an open source project to which I don't
contribute, DamageControl has never seemed to have a release stable enough
for production use. There is no longer a 'live' example DamageControl
running on the web I can point at to convince people what a great tool it
is. Tthe code is perpetually undergoing some sort of huge refactoring. Tthe
documentation is apparently scattered in pieces over the web at various
temporary homes (if its available at all), and getting up and running with
the latest and greatest version is obscure.

I realise that DamageControl is currently a one man effort - but I'm
impatient for something great to crystallise out of the project. Aslak, is
there anything I (?we) can do to help DamageControl move towards a stable
release? I can offer help coding help(although I'll have to spend a weekend
learning Ruby!) or testing help with both Perforce and ClearCase
repositories.

Is anybody actually succefully using DamageControl in a production
environment? If so can you please post which version and libraries you are
using?

Alternatively, can other list members suggest alternative tools I can use in
lieu of DamageControl until such time as DC is 'ready' ?

Many thanks,

Rob

[Chad Woolley]

I agree.  However, I know how extremely difficult it is to find the time to stay active on an open source project, especially when you have to do real work to pay the bills.  I'm a contributor to other open source projects which have tasks perpetually waiting for me to complete them.

I've formally volunteered for DamageControl and even discussed it with Aslak in person (at RubyConf) and email, but nothing has really happened yet, primarily because he didn't get back to me with a specific task he would like help with. 

Aslak said that getting a live sites up (stable and trunk) is a priority, and I agree.  I'll volunteer for this, or at least to the point where I reach something I can't configure or figure out (or this list can't help me).  So, I'd be glad to take responsibility for getting it up and running on the TextDrive account.  I can be trusted with the account, and I'll even give you references if you want :)

I'm also slowly getting my bearings with Ruby/Rails, so if Aslak wants to throw specific tickets at me I will try to tackle those too.

Thanks,
Chad

On 12/20/05, Robert Smallshire <robert@...> wrote:

I realise that DamageControl is currently a one man effort - but I'm
impatient for something great to crystallise out of the project. Aslak, is
there anything I (?we) can do to help DamageControl move towards a stable
release? I can offer help coding help(although I'll have to spend a weekend
learning Ruby!) or testing help with both Perforce and ClearCase
repositories.

[John Elrick]

I'll post this in general, I'm currently attempting to utilize DamageControl for a project with the Census Bureau.  I'm pretty experienced with Ruby and have started figuring out RoR.  I have the major advantage that configuring the server is considered part of our work, so I am doing real work while getting our build server up and running.

What I'm saying is that if you guys need another hand on this, let me know.


John Elrick
Fenestra Technologies

On 12/20/05, Chad Woolley <thewoolleyman@...> wrote:

I agree.  However, I know how extremely difficult it is to find the time to stay active on an open source project, especially when you have to do real work to pay the bills.  I'm a contributor to other open source projects which have tasks perpetually waiting for me to complete them.

I've formally volunteered for DamageControl and even discussed it with Aslak in person (at RubyConf) and email, but nothing has really happened yet, primarily because he didn't get back to me with a specific task he would like help with. 

Aslak said that getting a live sites up (stable and trunk) is a priority, and I agree.  I'll volunteer for this, or at least to the point where I reach something I can't configure or figure out (or this list can't help me).  So, I'd be glad to take responsibility for getting it up and running on the TextDrive account.  I can be trusted with the account, and I'll even give you references if you want :)

I'm also slowly getting my bearings with Ruby/Rails, so if Aslak wants to throw specific tickets at me I will try to tackle those too.

Thanks,
Chad

On 12/20/05, Robert Smallshire <robert@...> wrote:

I realise that DamageControl is currently a one man effort - but I'm
impatient for something great to crystallise out of the project. Aslak, is
there anything I (?we) can do to help DamageControl move towards a stable
release? I can offer help coding help(although I'll have to spend a weekend
learning Ruby!) or testing help with both Perforce and ClearCase
repositories.

[Robert Smallshire]

Hi folks,

Before I start pulling specific versions out of Subversion and installing
lots of different package versions I figured I try a straightforward install
according to the instructions at <http://damagecontrol.codehaus.org/>

The install went pretty much according to described - the only warnings were
regarding RDoc installations.

Then attempting to start DamageControl gives me a call-stack (below). Is
there any simple solution to this, or do I need to start trying to put a
working set of packages myself?

Cheers!

Rob

>damagecontrol -webbrick
C:/Program
Files/ruby/lib/ruby/gems/1.8/gems/activesupport-1.2.5/lib/active_supp
ort/dependencies.rb:200:in `const_missing': uninitialized constant Poller
(NameE
rror)
        from C:/Program
Files/ruby/lib/ruby/gems/1.8/gems/damagecontrol-0.5.0.14
04/lib/damagecontrol/app.rb:16
        from C:/Program
Files/ruby/lib/ruby/gems/1.8/gems/damagecontrol-0.5.0.14
04/lib/damagecontrol/app.rb:15:in `call'
        from C:/Program
Files/ruby/lib/ruby/gems/1.8/gems/needle-1.2.0/lib/needl
e/lifecycle/singleton.rb:42:in `call'
        from C:/Program
Files/ruby/lib/ruby/gems/1.8/gems/needle-1.2.0/lib/needl
e/lifecycle/singleton.rb:40:in `synchronize'
        from C:/Program
Files/ruby/lib/ruby/gems/1.8/gems/needle-1.2.0/lib/needl
e/lifecycle/singleton.rb:40:in `call'
        from C:/Program
Files/ruby/lib/ruby/gems/1.8/gems/needle-1.2.0/lib/needl
e/service-point.rb:117:in `instance'
        from C:/Program
Files/ruby/lib/ruby/gems/1.8/gems/needle-1.2.0/lib/needl
e/container.rb:308:in `get'
        from C:/Program
Files/ruby/lib/ruby/gems/1.8/gems/needle-1.2.0/lib/needl
e/container.rb:380:in `method_missing'
        from C:/Program
Files/ruby/lib/ruby/gems/1.8/gems/damagecontrol-0.5.0.14
04/lib/damagecontrol/app.rb:42:in `run'
        from C:/Program
Files/ruby/lib/ruby/gems/1.8/gems/damagecontrol-0.5.0.14
04/bin/damagecontrol:7
        from C:/Program
Files/ruby/lib/ruby/gems/1.8/gems/activesupport-1.2.5/li
b/active_support/dependencies.rb:207:in `load'
        from C:/Program
Files/ruby/lib/ruby/gems/1.8/gems/activesupport-1.2.5/li
b/active_support/dependencies.rb:207:in `load'
        from c:/Program Files/Ruby/bin/damagecontrol:18

[Robert Smallshire]

Doh!

My own fault - I misread damagecontrol-webrick as damagecontrol with a
command line option -webrick.

In any case I mistyped -webrick with two b's.  Doh! again!

Rob

> -----Original Message-----
> From: Robert Smallshire [mailto:robert@...]
> Sent: 29 December 2005 19:20
> To: user@...
> Subject: [damagecontrol-user] Getting up and running with DC 0.5
>
>
> Hi folks,
>
> Before I start pulling specific versions out of Subversion
> and installing lots of different package versions I figured I
> try a straightforward install according to the instructions
> at <http://damagecontrol.codehaus.org/>
>
> The install went pretty much according to described - the
> only warnings were regarding RDoc installations.
>
> Then attempting to start DamageControl gives me a call-stack
> (below). Is there any simple solution to this, or do I need
> to start trying to put a working set of packages myself?
>
> Cheers!
>
> Rob
>
> >damagecontrol -webbrick
> C:/Program
> Files/ruby/lib/ruby/gems/1.8/gems/activesupport-1.2.5/lib/active_supp
> ort/dependencies.rb:200:in `const_missing': uninitialized
> constant Poller (NameE
> rror)
>         from C:/Program
> Files/ruby/lib/ruby/gems/1.8/gems/damagecontrol-0.5.0.14
> 04/lib/damagecontrol/app.rb:16
>         from C:/Program
> Files/ruby/lib/ruby/gems/1.8/gems/damagecontrol-0.5.0.14
> 04/lib/damagecontrol/app.rb:15:in `call'
>         from C:/Program
> Files/ruby/lib/ruby/gems/1.8/gems/needle-1.2.0/lib/needl
> e/lifecycle/singleton.rb:42:in `call'
>         from C:/Program
> Files/ruby/lib/ruby/gems/1.8/gems/needle-1.2.0/lib/needl
> e/lifecycle/singleton.rb:40:in `synchronize'
>         from C:/Program
> Files/ruby/lib/ruby/gems/1.8/gems/needle-1.2.0/lib/needl
> e/lifecycle/singleton.rb:40:in `call'
>         from C:/Program
> Files/ruby/lib/ruby/gems/1.8/gems/needle-1.2.0/lib/needl
> e/service-point.rb:117:in `instance'
>         from C:/Program
> Files/ruby/lib/ruby/gems/1.8/gems/needle-1.2.0/lib/needl
> e/container.rb:308:in `get'
>         from C:/Program
> Files/ruby/lib/ruby/gems/1.8/gems/needle-1.2.0/lib/needl
> e/container.rb:380:in `method_missing'
>         from C:/Program
> Files/ruby/lib/ruby/gems/1.8/gems/damagecontrol-0.5.0.14
> 04/lib/damagecontrol/app.rb:42:in `run'
>         from C:/Program
> Files/ruby/lib/ruby/gems/1.8/gems/damagecontrol-0.5.0.14
> 04/bin/damagecontrol:7
>         from C:/Program
> Files/ruby/lib/ruby/gems/1.8/gems/activesupport-1.2.5/li
> b/active_support/dependencies.rb:207:in `load'
>         from C:/Program
> Files/ruby/lib/ruby/gems/1.8/gems/activesupport-1.2.5/li
> b/active_support/dependencies.rb:207:in `load'
>         from c:/Program Files/Ruby/bin/damagecontrol:18
>
>
>
>