Use git instead of svn for install_dependencies and update_dependencies
Reported by Brian Takita | April 20th, 2008 @ 05:06 PM | in 1.1.4
Since rails is using git, we can do a git close on the rails projects.
Comments and changes to this ticket
-
David Chelimsky April 21st, 2008 @ 05:40 AM
git clone?
-

Brian Takita April 22nd, 2008 @ 01:15 AM
Yes. Git clone. Braid is also nice.
A simple braindead way of doing this is to close the rails repo for each version. Of course that would be expensive.
Can we export from a tag from a repo in Git?
-
Ian White April 22nd, 2008 @ 08:40 AM
IMHO clone would be better than braid, given that this is for CI stuff. (braid if you want to check it in, and braid is sloooow)
Maybe just clone the one repo in vendor/rails, and hook up the pre_commit script to checkout different branches before each run. If this would work, then there is the advantage of not monkey patching config/boot.rb
-
David Chelimsky April 22nd, 2008 @ 10:34 AM
+1 on the single repo. That would simplify things a great deal.
-
Ian White April 24th, 2008 @ 03:42 PM
Ok, I've been experimenting with using local git repos to help with CI.
I've stuck it all in here: http://github.com/ianwhite/garlic
My approach is to actually create different rails apps (as opposed to having one app with different vendors).
Because the repos are all local, this is fast and easy. I've created a mini-dsl which simply allows specification of repos, rails targets, plugins, and any prepare code that needs to be done. There is room for more stuff.
I've actually applied it it one of my own plugins
http://github.com/ianwhite/inher... it seems to work pretty good.
Just clone it, and run rake cruise, everything gets downloaded and run.
I think this approach could work for rspec, it seems to me that a lot of the cruft in the pre_commit stuff comes from trying to maintain the different rails versions within one app. This approach just builds a new app each time.
This is like 3 hours old, so there's plenty of room for improvement (and specing).
Cheers,
Ian
-
Ian White April 24th, 2008 @ 04:13 PM
I just wrote a small blog entry on it
-
David Chelimsky April 29th, 2008 @ 12:09 AM
- → Milestone changed from No-Milestone-Assigned to 1.1.4
- → State changed from new to resolved
OK - 'tis using git clone now. Multirails.rake checks out the different tags.
Not working w/ edge right now, but that's a separate matter.
Please Login or create a free account to add a new comment.
You can update this ticket by sending an email to from your email client. (help)
Behaviour Driven Development for Ruby.
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
