Using GIT w/CC.RB

[Kevin Willock]

Hi there, I am new here, but haven't seen an archive so I'm sorry if  
this question has been asked before.

I have installed the weplay master from githum, and set up my project  
via

./cruise add project -r git.project.com:/location -s git

The project is checked out fine, but on the cc.rb page, it displays  
the error

"svn_error unknown state"
"svn: '.' is not a working copy"

And the builder is listed as down.

If I do a manual build, it will use the same build # and append a .#  
to it, and the builder is listed as fine after. Once a new file is  
pushed to the git repo, the SVN error re-appears...

Is there a way to get cc.rb to automatically build, upon a git push?

Thanks

-k

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

[Alexey Verkhovsky-2]

On Thu, Oct 9, 2008 at 2:32 PM, Kevin Willock <xipher1@...> wrote:
> Is there a way to get cc.rb to automatically build, upon a git push?

It's in the works, and will be in the next release.

Meantime, there is Ben Burkert's branch that already supports this,
and many people use it for the same purpose.
Google for "cc.rb git", and the very first hit tells you how to
install it: http://codeintensity.blogspot.com/2008/04/setting-up-cruisecontrolrb-withfor-git.html

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

[Kevin Willock]

On 9-Oct-08, at 2:44 PM, Alexey Verkhovsky wrote:

> On Thu, Oct 9, 2008 at 2:32 PM, Kevin Willock <xipher1@...>  
> wrote:
>> Is there a way to get cc.rb to automatically build, upon a git push?
>
> It's in the works, and will be in the next release.
>
> Meantime, there is Ben Burkert's branch that already supports this,
> and many people use it for the same purpose.
> Google for "cc.rb git", and the very first hit tells you how to
> install it: http://codeintensity.blogspot.com/2008/04/setting-up-cruisecontrolrb-withfor-git.html

Thanks Alexey, do we know when the next release is slated for?

I tried those directions initially, but the same problems occurred, I  
will go through them again. There are lots of benefits towards moving  
to git, but if we lose CI, then it isn't worthwhile...

-k

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

[Alexey Verkhovsky-2]

On Thu, Oct 9, 2008 at 2:57 PM, Kevin Willock <xipher1@...> wrote:
> Thanks Alexey, do we know when the next release is slated for?
Not really. It can be anywhere between a couple of weeks and a couple of months.

> I tried those directions initially, but the same problems occurred

That's unfortunate. People are using Ben's branch on projects, as far
as I know, so maybe someone else on the list may help you there.

Jeremy Lightsmith told me a couple of days ago that he is using CC.rb
trunk on a project with Git, after some changes (that he has checked
in already), and it works for them. So, if Ben's branch doesn't work
for you, perhaps you can try the trunk instead.

Sorry for not being very helpful.

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

[Jeremy Lightsmith]

if you do try trunk, please let us know how it goes, because we are relying on user feedback to get what's on trunk stable enough for a new release!

Jeremy

On Thu, Oct 9, 2008 at 3:05 PM, Alexey Verkhovsky <alexey.verkhovsky@...> wrote:

On Thu, Oct 9, 2008 at 2:57 PM, Kevin Willock <xipher1@...> wrote:
> Thanks Alexey, do we know when the next release is slated for?

Not really. It can be anywhere between a couple of weeks and a couple of months.

> I tried those directions initially, but the same problems occurred

That's unfortunate. People are using Ben's branch on projects, as far
as I know, so maybe someone else on the list may help you there.

Jeremy Lightsmith told me a couple of days ago that he is using CC.rb
trunk on a project with Git, after some changes (that he has checked
in already), and it works for them. So, if Ben's branch doesn't work
for you, perhaps you can try the trunk instead.

Sorry for not being very helpful.

-- Alex

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

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

[Kevin Willock]

Alexey and Jeremy, thanks for the help so far! I got both trunk and  
Ben's branch working, the problem was with my ssh keys (imagine my  
embarassment)
I am using trunk now, but the problem I am having is that it is not  
sending emails... Everything else seems to be working just dandy. If  
you guys have any insight into the email issue

in config/site_config.rb:
> ActionMailer::Base.smtp_settings = {
>    :address =>        "localhost",
>    :domain =>         "[domain]",
>  }

The Trace;

> executed command :
>
> echo /var/www/cruise/work/projects/test/work test_deploy
> $ ruby -e "require 'rubygems' rescue nil;
> require 'rake';
> load '/var/trustme/www/cruise/tasks/cc_build.rake';
> ARGV << '--nosearch' << '--trace' << 'cc:build';
> Rake.application.run; ARGV.clear" >> /var/www/cruise/work/projects/
> test/build-85ca435/build.log &&
> ruby -e "require 'rubygems' rescue nil;
> require 'rake'; load '/var/www/cruise/tasks/cc_build.rake';
> ARGV << '--nosearch' << '--trace' << 'cc:build';
> Rake.application.run;
> ARGV.clear" >> /var/www/cruise/work/projects/test/build-85ca435/
> build.log 2>&1
> exitstatus: 1
> STDERR TAIL START
> STDERR TAIL END
> [debug]   ./script/../config/../lib/command_line.rb:146:in  
> `verify_exit_code'
> [debug]   ./script/../config/../lib/command_line.rb:95:in `e'
> [debug]   ./script/../config/../lib/command_line.rb:71:in `execute'
> [debug]   ./script/../config/../lib/command_line.rb:70:in `chdir'
> [debug]   ./script/../config/../lib/command_line.rb:70:in `execute'
> [debug]   ./script/../config/../app/models/build.rb:31:in `run'
> [debug]   ./script/../config/../app/models/build.rb:185:in `call'
> [debug]   ./script/../config/../app/models/build.rb:185:in  
> `in_clean_environment_on_local_copy'
> [debug]   ./script/../config/../app/models/build.rb:184:in `chdir'
> [debug]   ./script/../config/../app/models/build.rb:184:in  
> `in_clean_environment_on_local_copy'
> [debug]   ./script/../config/../app/models/build.rb:30:in `run'
> [debug]   ./script/../config/../app/models/project.rb:310:in  
> `build_without_serialization'
> [debug]   ./script/../config/../app/models/project.rb:287:in `build'
> [debug]   ./script/../config/../app/models/project.rb:211:in  
> `build_if_necessary'
> [debug]   ./script/../config/../app/models/polling_scheduler.rb:
> 13:in `run'
> [debug]   ./script/builder:79
> [debug]   ./script/builder:78:in `catch'
> [debug]   ./script/builder:78
> [debug]   script/../config/../cruise:14:in `load'
> [debug]   script/../config/../cruise:14:in `builder'
> [debug]   script/../config/../cruise:68:in `send'
> [debug]   script/../config/../cruise:68
> [debug]   /usr/lib/ruby/1.8/fileutils.rb:121:in `chdir'
> [debug]   /usr/lib/ruby/1.8/fileutils.rb:121:in `cd'
> [debug]   script/../config/../cruise:67
> Build 85ca435 FAILED
> [info]  [2008-10-09 15:35:28] Build 85ca435 FAILED
> [debug] [2008-10-09 15:35:28] Sleeping

And tailing maillog reveals no attempts to send an email.

Thoughts?

-k


On 9-Oct-08, at 4:05 PM, Alexey Verkhovsky wrote:

> On Thu, Oct 9, 2008 at 2:57 PM, Kevin Willock <xipher1@...>  
> wrote:
>> Thanks Alexey, do we know when the next release is slated for?
> Not really. It can be anywhere between a couple of weeks and a  
> couple of months.
>
>> I tried those directions initially, but the same problems occurred
>
> That's unfortunate. People are using Ben's branch on projects, as far
> as I know, so maybe someone else on the list may help you there.
>
> Jeremy Lightsmith told me a couple of days ago that he is using CC.rb
> trunk on a project with Git, after some changes (that he has checked
> in already), and it works for them. So, if Ben's branch doesn't work
> for you, perhaps you can try the trunk instead.
>
> Sorry for not being very helpful.
>
> -- Alex
> _______________________________________________
> Cruisecontrolrb-users mailing list
> Cruisecontrolrb-users@...
> http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users

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

[Alexey Verkhovsky-2]

On Thu, Oct 9, 2008 at 4:12 PM, Kevin Willock <xipher1@...> wrote:
> And tailing maillog reveals no attempts to send an email.
> Thoughts?

What is your cruise_config.rb look like?

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

[Kevin Willock]

It's pretty simple

> Project.configure do |project|
> project.email_notifier.emails = ['email@...']
> project.email_notifier.from = 'cruise@...'
> project.scheduler.polling_interval = 5.minutes
> end

-k

On 9-Oct-08, at 4:24 PM, Alexey Verkhovsky wrote:

> On Thu, Oct 9, 2008 at 4:12 PM, Kevin Willock <xipher1@...>  
> wrote:
>> And tailing maillog reveals no attempts to send an email.
>> Thoughts?
>
> What is your cruise_config.rb look like?
>
> -- Alex
> _______________________________________________
> Cruisecontrolrb-users mailing list
> Cruisecontrolrb-users@...
> http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users

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

[Matt Wynne]

We're using it at songkick and it's going fine - thanks for your  
efforts Jeremy, especially to get the commit messages in there. Now we  
know who to blame, which is the main thing ;)

I guess my only negative feedback is that some support for submodules  
(automatically doing git submodule init / update after pulling) would  
be nice, but we're happy doing that manually as and when required.

On 9 Oct 2008, at 23:12, Jeremy Lightsmith wrote:

> if you do try trunk, please let us know how it goes, because we are  
> relying on user feedback to get what's on trunk stable enough for a  
> new release!
>
> Jeremy
>
> On Thu, Oct 9, 2008 at 3:05 PM, Alexey Verkhovsky <alexey.verkhovsky@...
> > wrote:
> On Thu, Oct 9, 2008 at 2:57 PM, Kevin Willock <xipher1@...>  
> wrote:
> > Thanks Alexey, do we know when the next release is slated for?
> Not really. It can be anywhere between a couple of weeks and a  
> couple of months.
>
> > I tried those directions initially, but the same problems occurred
>
> That's unfortunate. People are using Ben's branch on projects, as far
> as I know, so maybe someone else on the list may help you there.
>
> Jeremy Lightsmith told me a couple of days ago that he is using CC.rb
> trunk on a project with Git, after some changes (that he has checked
> in already), and it works for them. So, if Ben's branch doesn't work
> for you, perhaps you can try the trunk instead.
>
> Sorry for not being very helpful.
>
> -- Alex
> _______________________________________________
> Cruisecontrolrb-users mailing list
> Cruisecontrolrb-users@...
> http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users
>
> _______________________________________________
> Cruisecontrolrb-users mailing list
> Cruisecontrolrb-users@...
> http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users

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

[Chad Woolley]

On Fri, Oct 10, 2008 at 1:00 AM, Matt Wynne <matt@...> wrote:
> I guess my only negative feedback is that some support for submodules
> (automatically doing git submodule init / update after pulling) would be
> nice, but we're happy doing that manually as and when required.

Just checked this in.  Try it out in master branch:

https://cruisecontrolrb.lighthouseapp.com/projects/9150/tickets/234-no-git-submodule-support
_______________________________________________
Cruisecontrolrb-users mailing list
Cruisecontrolrb-users@...
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users

[Matt Wynne]

On 12 May 2009, at 02:09, Chad Woolley wrote:

> On Fri, Oct 10, 2008 at 1:00 AM, Matt Wynne <matt@...>  
> wrote:
>> I guess my only negative feedback is that some support for submodules
>> (automatically doing git submodule init / update after pulling)  
>> would be
>> nice, but we're happy doing that manually as and when required.
>
> Just checked this in.  Try it out in master branch:
>
> https://cruisecontrolrb.lighthouseapp.com/projects/9150/tickets/234-no-git-submodule-support

Thanks for your efforts Chad, I'm afraid I have defected :)

http://blog.mattwynne.net/2009/04/21/goodbye-cruisecontrolrb-hello-hudson/

Matt Wynne
http://blog.mattwynne.net
http://www.songkick.com

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