Code deployment and build management

You are viewing a wiki page. You are welcome to join the group and then edit it. Be bold!

Posted by senpai on December 9, 2008 at 4:40pm
Last updated by silverwing on Thu, 2011-07-14 22:04

Here's a group of modules that seem to be heading rapidly toward the same goal(s):

I've encouraged collaboration between the deploy & autopilot module's developers several times, but so far nothing's taken place.

Comments

http://drupal.org/project/dbscripts

Posted by greggles on December 9, 2008 at 10:27pm

and http://drupal.org/project/dbscripts

I'm starting to think that we should start all of these threads as wikis so that we can update them as time goes by and work to compare them like (http://groups.drupal.org/node/12347 and http://groups.drupal.org/node/15928 have done).

If folks agree we can probably get moshe to flip the switch so that the existing threads instantly become wikis.

We would also want to leave a message in the mission block requesting that these be wikis.

knaddison blog | Morris Animal Foundation

good idea

Posted by catch on December 9, 2008 at 11:00pm

I'm able to enable comments on wikis now, so happy to do that when people post them.

yay

Posted by greggles on December 19, 2008 at 12:01am

Thanks to Moshe and dww this is now done. Be bold, everyone!

knaddison blog | Morris Animal Foundation

Actually they are all quite different

Posted by mikey_p on December 19, 2008 at 12:56am

I would say that they are all quite different and important.

DB scripts is the only one that I know of that can merge two databases with entirely separate content. (note that it is not actually a module).

Deploy is probably the simplest to use and uses two sites and allows changes on one site to be played back on another site, in a macro recorder type of fashion. This is great for settings and such, but as handy as DB scripts for large amounts of content/users, or user generated content(non-admin).

Autopilot is in another class altogether and is designed to be able to make it easy to push files (code) and databases to multiple targets (different web servers) and run scripts in the process and make change to each for the purposes of maintaining multiple sites (test,dev,qa, prod) and it also integrates with logging, ssh, and subversion. Autopilot probably be used to deploy non-Drupal code just as easily, yet it runs in a dedicated Drupal site for managing permissions and access to deployments.

Each one has their own strength, and I'd say this is not an area where we have a clear enough idea of what is best, or even what all the possible solutions are to say that there is duplication of modules. I could easily see using at least two of these, if not all three together in some combination and not really duplicating any functionality.