Matt Wynne wrote:
On 3 Sep 2008, at 12:11, Jay Levitt wrote:
I'm new to both CCrb and git. I pulled down the latest from the master
thoughtworks repository on github, and after a few quick tweaks, I had
a CCrb instance and running on mod_passenger. I added a project, a
few more tweaks, it built. So far, so good!
Here, though, are the things I'm not clear on...
1. When I set up my new project, I added it as
./cruise add projectname --repository [EMAIL PROTECTED]:projectname.git
--source-control git
Where do these parameters get stored? I don't see any external
managment of them. They go into the Project model, but there's no
database.yml, so from there, I'm lost Are they a side effect of
CRUISE_DATA_ROOT/projects having a subfolder named for each project?
Exactly. If you look at the code in app/model/Project, it just looks at
the sub-folders of CRUISE_DATA_ROOT/projects and tries to load a project
from each one. Cruise is basically using the file-system as its
database, which is actually pretty neat - you can delete old build, for
example, just by deleting the build-* folder in your project's folder.
Yes, that is nice and clean.. you don't have to keep things in sync if you
rely on the underlying data in the first place!
Where does it store things like the repository name, scm type, etc? I did
an "ack --all -i git /srv/cruiserb --ignore-dir=work", and came up with zilch.
3. Now that it's built... it built once, said it was happy, and that's
it. I can do a manual build via the web interface, and it works, but
it doesn't pull any new code down from the master (which is on the
same server, as username git). The automatic build, which is supposed
to poll every 20 seconds for updates, doesn't seem to have done
anything; here again, I'm hampered by not knowing what to look for.
The logs don't contain the string "git" at all. Where is that pull
supposed to occur?
Sorry, can't help you with this one - ours works fine. I guess you need
to check that the builder processes are running under an account with
sufficient permission on your git repo folders. How exactly did you
reference the repository? If you're on the same machine you can use file
paths which might make things simpler:
e.g. ./cruise add projectname --repository /home/git/projectname --
source-control git
Ah, interesting. I'm running CC under mod_rails/Passenger, and I've noticed
some builder oddities; for instance, it loses track of its builder when I
restart Apache, and then, naturally, it complains about the lock file.
I will try switching to a plain-old Ruby cruiserb daemon and see if that
solves the problem. I was using an ssh-style path for the repository - e.g.
./cruise add project --repository [EMAIL PROTECTED]:project.git
--source-control git
which worked well enough to pull the changes in the first place, but maybe
that doesn't work for future pull requests, for whatever reason. I'll try
the filesystem path instead.
Thanks for any pointers..
Jay Levitt
_______________________________________________
Cruisecontrolrb-users mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users
HTH
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
