Drupal Answers is a question and answer site for Drupal developers and administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I do a lot of web consulting and drupal is my preferred tool of choice. But as I grow, it seems like drupal gets more and more needy. At least once a week, if not more, my inbox gets messages that drupal needs updating, and I have to go and update the dev server, verify nothing broke, and then update the production server, and again verify that nothing broke.

I'm using drush to help me with this, but this is still taking considerable time away from my business, time I could be billing to the customer.

Does anyone have a solution to this? Some way to automate the updates and then a regression test, and if successful, do the same on production?

share|improve this question

You could write scripts to do this. You'd probably want to tie in to the Drupal unit testing module as well.

I can't provide you with any actual examples, because I'm not sure how it would be done reliably.

In my opinion, you're looking at a business problem that can't be fixed with a programming solution. If I were in your shoes, I would start charging customers an ongoing maintenance fee for upgrades.

share|improve this answer

I use the following script:


n.b. not guaranteed to be bug-free. The "verify nothing broke" and "update the production server" are manual steps, but at least my update sites are available for testing when I want to do it.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.