change management

Hello everyone,

I have been "messing" with drupal for a while now, and have now taken my first job as a 100% committed Drupal developer & tech lead for a company that builds massive websites for large federal initiatives that involve dense structures, complex role management schemes, and mountains of content (often 10,000+ nodes).

So, one of my first tasks as we get started is to work with the site building team and sys admins to create a solid process for performing migrations from dev >>> staging, sometimes staging >>> dev, and, of course, the eventual staging >>> production.

Hi Techies, Drupul Geeks ... and Newspaper Content Managers--

hi,

i've just created a Settings Audit Log module.

http://drupal.org/project/settings_audit_log

it uses a trigger on variable to log all changes by user.

looking for reviews, feedback, and ideas for modules to build on top of this using the audit data.

cheers
justin

We are trying to integrate Patterns execution in our change management system based on Liquibase. It seems like the Patterns module only supports execution in GUI mode. Is there any way to execute them from command line or any API we can use to create a Drush extension?

Does the Configuration Framework try to cover these use cases? If so, what's its current development status and where should we start looking for more information?

Thanks a lot!

Esteban

Hi folks,

it seems this group stalled a little bit, so lets try to give it some activity :-) I was wondering if this group has already collected some best practices around Drupal deployment and change management. So far, I have only found best practices for managing the source code of a drupal site, but I have not found anything how to transport configuration changes (done in the DB) from a devel environment to a production environment. As far as I can see there are no stable modules or scripts for that, at least not for D6. Any ideas where to look?

Regards,

Sebastian

[copied from my WorkHabit blog post]

We had a great time at the S.D. Drupal User Group meetup this month. there were almost 20 people in attendance this time, including Myself, Michael Murdoch, and Harry Slaughter, the latter of whom you would expect to be there because he was the impetus and organizer! I even saw some of the Achieve Internet gang there, including Alex Villeux and Karl Scheirer, my former supervisors. Awesome! A few of the gang from Achieve's Costa Rican development office were up for the week, and I got to hang out with them for a little bit too. <href="http://drupal.org/user/208711">Nestor Mata is a Central American codehead who I had the pleasure of working with on the http://namm.org project (he built the Rotor module, among others) and it was great to finally meet him face to face. Cheers, Nestor!

Hey folks,

I've worked on a number of Drupal sites where we needed to keep multiple sites in synch, and Drupal has been a challenge to keep that way because so many options are changed through the UI - this tends to show its weakness when we want to keep the settings across all sites (don't even mention content). Moving content types and views is easy with the import/export tools, but blocks are another story. The visibility rules, Roles, and input formats all require your time and attention to detail - time you could be spending working on other features.

I have been working on a framework that attempts to address some of the issues of deploying code and data in Drupal. It is outlined here:

http://heyrocker.com/drupal/content/deployment-and-change-management-fra...

I'd love to hear people's thoughts on this.

Is anyone interesting in having a brainstorming session on deployment and change/build management at Drupalcon Boston? This could either be an officially submitted proposal with an open agenda, or an unofficial get together in a side room at the conference center. It seems like a lot of us are struggling with enterprise-level deployment issues, and getting a bunch of smart and interested people in a room talking about their own solutions and brainstorming new ones would be useful for everyone. We all have our own ways of handling it and I'd love to hear other people's ideas.