It seems to happen to us every few days since moving from the benburket fork that the our project just builds repeatedly. I''m going to try http://github.com/willbryant/cruisecontrolrb/commits/ master Does anyone have plans / time to merge these changes into the main throughworks trunk? it seems a shame it doesn''t have the latest and greatest, and the git support in there is pretty sketchy (no commit messages, etc). I don''t mean to whine, and when I get some time I''ll be happy to do this myself. cheers, Matt ---- http://blog.mattwynne.net http://songkick.com In case you wondered: The opinions expressed in this email are my own and do not necessarily reflect the views of any former, current or future employers of mine. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/cruisecontrolrb-users/attachments/20080917/a6f3cf8e/attachment-0001.html>
Hey, Alexey worked with me last week, but was unable to reproduce the repeated-build bug, I only see it when I set up a new ccrb install and add a new project. Do you have a specific scenario to recreate the multiple build problem in a clean environment? Since it only happened for me on project add, I didn''t think it was a big issue, but if it happens all the time for you, we should identify the exact cause. Also, on the commit set messages, I know Alexey started them last week but is not finished. Maybe he can put them up in a branch on the thoughtworks account, and people can fork and help out? So, as far as I know, these are the only two outstanding git issues, and as I said, Alexey couldn''t recreate the repeated-build problem. You should open tickets for any other issues on lighthouse, and tag them with ''git''. -- Chad On Wed, Sep 17, 2008 at 7:26 AM, Matt Wynne <matt at mattwynne.net> wrote:> It seems to happen to us every few days since moving from the benburket fork > that the our project just builds repeatedly. > I''m going to try http://github.com/willbryant/cruisecontrolrb/commits/master > Does anyone have plans / time to merge these changes into the main > throughworks trunk? it seems a shame it doesn''t have the latest and > greatest, and the git support in there is pretty sketchy (no commit > messages, etc). > I don''t mean to whine, and when I get some time I''ll be happy to do this > myself. > > cheers, > Matt > ---- > http://blog.mattwynne.net > http://songkick.com > In case you wondered: The opinions expressed in this email are my own and do > not necessarily reflect the views of any former, current or future employers > of mine. > > > > _______________________________________________ > Cruisecontrolrb-users mailing list > Cruisecontrolrb-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users > >
On 17 Sep 2008, at 18:10, Chad Woolley wrote:> Hey, > > Alexey worked with me last week, but was unable to reproduce the > repeated-build bug, I only see it when I set up a new ccrb install and > add a new project. Do you have a specific scenario to recreate the > multiple build problem in a clean environment? Since it only happened > for me on project add, I didn''t think it was a big issue, but if it > happens all the time for you, we should identify the exact cause.Patterns will hopefully emerge as we use it more. When I was trying to resolve it today, I went into the work folder for the build project, tried git pull and git reckoned it needed to merge... which seemed insane, since nobody had changed anything on the local copy. I ended up deleting the work folder and re-cloning it - and everything was OK again. One theory I have: - if several people check in in close succession, such that there are new check-ins while a build is already running, will it try to pull again while the first build is running and get confused? Maybe it would be useful to be able to turn on a log of git commands issued so we can pull it to pieces next time it goes silly-buggers.> Also, on the commit set messages, I know Alexey started them last week > but is not finished. Maybe he can put them up in a branch on the > thoughtworks account, and people can fork and help out?That would be good. I took a look at the willbryant fork today but it''s missing quite a lot of the nice stuff in the main thoughtworks trunk like the daemon_helper script, and branching support for git, but the revisions stuff seems to be done, so I did think about patching> So, as far as I know, these are the only two outstanding git issues, > and as I said, Alexey couldn''t recreate the repeated-build problem. > You should open tickets for any other issues on lighthouse, and tag > them with ''git''. > > -- Chad > > On Wed, Sep 17, 2008 at 7:26 AM, Matt Wynne <matt at mattwynne.net> > wrote: >> It seems to happen to us every few days since moving from the >> benburket fork >> that the our project just builds repeatedly. >> I''m going to try http://github.com/willbryant/cruisecontrolrb/ >> commits/master >> Does anyone have plans / time to merge these changes into the main >> throughworks trunk? it seems a shame it doesn''t have the latest and >> greatest, and the git support in there is pretty sketchy (no commit >> messages, etc). >> I don''t mean to whine, and when I get some time I''ll be happy to >> do this >> myself. >> >> cheers, >> Matt >> ---- >> http://blog.mattwynne.net >> http://songkick.com >> In case you wondered: The opinions expressed in this email are my >> own and do >> not necessarily reflect the views of any former, current or future >> employers >> of mine. >> >> >> >> _______________________________________________ >> Cruisecontrolrb-users mailing list >> Cruisecontrolrb-users at rubyforge.org >> http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users >> >> > _______________________________________________ > Cruisecontrolrb-users mailing list > Cruisecontrolrb-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-userscheers, Matt ---- http://blog.mattwynne.net http://songkick.com In case you wondered: The opinions expressed in this email are my own and do not necessarily reflect the views of any former, current or future employers of mine.
On Wed, Sep 17, 2008 at 3:08 PM, Matt Wynne <matt at mattwynne.net> wrote:> That would be good. I took a look at the willbryant fork today but it''s > missing quite a lot of the nice stuff in the main thoughtworks trunk like > the daemon_helper script, and branching support for git, but the revisions > stuff seems to be done, so I did think about patchingThere is still some work that could be done on the daemon helper. CCRB has some "bugs" in how it handles the pid files. It should do a port check and kill the existing pid file if nothing is running, rather than just dying. This causes mysterious problems on reboot. This is what mongrel_cluster does.
Alexey Verkhovsky
2008-Sep-18 15:44 UTC
[Cruisecontrolrb-users] build going bananas with git
Commit messages were added to the main trunk a couple of weeks ago.> It seems to happen to us every few days since moving from the > benburket fork that the our project just builds repeatedly.I would really love to find out how to reproduce this problem. Never happened to me so far.> I''m going to tryhttp://github.com/willbryant/cruisecontrolrb/commits/master> Does anyone have plans / time to merge these changes into the > main throughworks trunk?Haven''t got any patches or pull requests from this fork so far. -- Alex
Alexey Verkhovsky
2008-Sep-18 15:50 UTC
[Cruisecontrolrb-users] build going bananas with git
> git reckoned it needed to merge...Hmm... interesting!>Maybe it would be useful to be able to turn on a log of git commandsIf you run it with --trace option, it should put git commands into the log. -- Alex
Jeremy Lightsmith
2008-Sep-18 16:05 UTC
[Cruisecontrolrb-users] build going bananas with git
maybe a sensible feature request would be to allow a project''s cruise_config.rb file to switch the builders into trace mode. It''s currently a bit hard to figure out how to do this for someone new, I think Jeremy On Thu, Sep 18, 2008 at 8:50 AM, Alexey Verkhovsky < averkhov at thoughtworks.com> wrote:> > git reckoned it needed to merge... > Hmm... interesting! > > >Maybe it would be useful to be able to turn on a log of git commands > If you run it with --trace option, it should put git commands into the log. > -- Alex > > _______________________________________________ > Cruisecontrolrb-users mailing list > Cruisecontrolrb-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/cruisecontrolrb-users/attachments/20080918/1fc88fa5/attachment.html>
On 18 Sep 2008, at 16:50, Alexey Verkhovsky wrote:>> git reckoned it needed to merge... > Hmm... interesting!And completely nonsensical. Any tips on git commands I could run to post-mortem this if I see it again? Any thoughts on my multi-check-in theory?> >> Maybe it would be useful to be able to turn on a log of git commands > If you run it with --trace option, it should put git commands into > the log. > -- Alexas in /etc/init.d/cruise start --trace ? cheers, Matt ---- http://blog.mattwynne.net http://songkick.com In case you wondered: The opinions expressed in this email are my own and do not necessarily reflect the views of any former, current or future employers of mine.
Jeremy Lightsmith
2008-Sep-18 16:34 UTC
[Cruisecontrolrb-users] build going bananas with git
nope, as I said, it''s a bit weird. you''ll have to start the builder before starting cruise w/ "./cruise builder MyProject --trace" I think On Thu, Sep 18, 2008 at 9:24 AM, Matt Wynne <matt at mattwynne.net> wrote:> On 18 Sep 2008, at 16:50, Alexey Verkhovsky wrote: > > git reckoned it needed to merge... >>> >> Hmm... interesting! >> > > And completely nonsensical. Any tips on git commands I could run to > post-mortem this if I see it again? > > > Any thoughts on my multi-check-in theory? > > >> Maybe it would be useful to be able to turn on a log of git commands >>> >> If you run it with --trace option, it should put git commands into the >> log. >> -- Alex >> > > as in > > /etc/init.d/cruise start --trace > > ? > > cheers, > Matt > ---- > http://blog.mattwynne.net > http://songkick.com > > In case you wondered: The opinions expressed in this email are my own and > do not necessarily reflect the views of any former, current or future > employers of mine. > > > > _______________________________________________ > Cruisecontrolrb-users mailing list > Cruisecontrolrb-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/cruisecontrolrb-users/attachments/20080918/a2453604/attachment-0001.html>
Alexey Verkhovsky
2008-Sep-18 20:30 UTC
[Cruisecontrolrb-users] build going bananas with git
cruisecontrolrb-users-bounces at rubyforge.org wrote on 09/18/2008 10:34:30 AM:> nope, as I said, it''s a bit weird. you''ll have to start the builder > before starting cruise w/ "./cruise builder MyProject --trace"No, "cruise start --trace" will pass the --trace option to builder processes. That will put the actual commands into the log. Or you can look at git.rb and see those command in the source code. -- Alex -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/cruisecontrolrb-users/attachments/20080918/2191b53d/attachment.html>
On Thu, Sep 18, 2008 at 8:44 AM, Alexey Verkhovsky <averkhov at thoughtworks.com> wrote:> Commit messages were added to the main trunk a couple of weeks ago.Are you sure? The last change I see on the github master is 8/15, over a month ago. Did you push to origin?