How to keep team members up to speed with manual changes using a simple list

Description

Collection: Change Management and Version ControlChapter: How To Manage Non-Exportable Configuration Changes

Transcript

Now, we have two test cases in our assets folder ready to be added to version control so that other people can run them on their environments to bring their environments up-to-date. And so eventually, we can run those on production in order to bring production up-to-date. But how does everybody know exactly what steps they need to take.

While these tests speed up the process of running through configuration changes they still need to be triggered manually. So in any project when you're working on a team, you'll need some way to keep track of these manual changes. Now, the tools we've covered, features in Selenium, will help reduce the number of manual steps greatly, but we still have a few things we need to do.

So for example, if Gary, our coworker needs to get up-to-date with the changes, they'll need to enable the feature module, the blog feature module and then run these two tests. So one solution is to just keep an ongoing list somewhere in your version control system so that it's shared and you can see exactly what changes were made to that list when so you know when to apply those changes. So let's go ahead and use a file like that.

If you jump back to our resource pack directory, go ahead and copy over the manual-updates dot text file and then go o ...

In this series we uncover how to use powerful tools to speed up and stabilize the Drupal development process. We begin with a thorough walk-through of Git, the version control system. After we cover how to patch modules and upgrade Drupal from one minor version to another, we demonstrate how to use the Features module to version control components of Drupal that aren't typically available to version control. Finally, we wrap up with how to integrate Drush - a powerful command line tool for Drupal - into your workflow to speed up the process of doing everything we discussed earlier in the series.

Some of the key points we'll be covering include:

How to use the command line

How to work with the Features module to capture important database changes and make deployment easier.

How to use Git for version control

Best practices for working on a Drupal team

Who this collection is for

This video collection is mainly for developers who want to improve their deployment strategies and learn how to work on a shared Drupal code base with other developers. However, even if you are not a developer, our coverage of using Features and version control is extremely valuable for deploying Drupal sites and sharing reusable components between projects.

Prerequisites

Even if you are not a developer, you will be able to follow with most of this collection. When we talk about code we do not go into detail about the basic components of the code, so you may want to brush up on some coding basics in the "PHP Programming Basics" collection.

It looks like there might be an issue playing videos in this browser. We're working on better cross-brower experience, but in the meantime please try the latest Chrome or Firefox browsers. Or, you may be able to watch the video directly without progress tracking or transcript: