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 <[EMAIL PROTECTED]>
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
[email protected]
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users
_______________________________________________
Cruisecontrolrb-users mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users
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
[email protected]
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users