You guys aware of this effort?
https://github.com/msonnabaum/vagrant-drush-ci

Cheers

Comments

glennpratt’s picture

glennpratt commented
Title: Another effort underway » How can we collaborate on or abstract the 'recipes' used in the vagrant project.

Of course, msonnabaum is my arch nemesis!

I think he is working on an automated testing environment for drush there, so something to keep an eye on, but not quite the same.

This does bring up a difficult problem though, how can we collaborate on config management 'recipes' when we keep duplicating them in different projects? I've asked Opscode about this, but I didn't get a particularly helpful response, at least for open source projects.

patcon’s picture

patcon commented

haha arch nemeses are the spice of life.

And yeah, it seems like there's some sort of solution in git submodules, but not even opscode have embraced that. It seems chef users right now are keeping one clone of the virgin chef-repo from github, with all their cookbooks in that (custom and shared), and also keeping individual personal repos for their custom cookbooks.

Not sure how submodules look on github (or drupalcode.org, for that matter)... I lean toward using github as the canonical resource (although that's pretty arbitrary)

patcon’s picture

patcon commented

Seems relevant, so just a heads up in case you want to have at er'
https://github.com/jnewland/split_cookbooks/issues/3

And the cookbooks org that is being referred to in the thread is here (the repo that the issue is on is for the ruby script that maintains the org):
https://github.com/cookbooks