The updating procedure for both SSWEs and PWEs is very similar. When updating both types of working environments, we strongly suggest that you follow these general guidelines: (The updating instructions later on in the chapter are based on these guidelines.)
Workspace projects
Rollback in case of unsuccessful builds in the SOWE
Builds in a SOWE are not always successful, especially if one of your team members has checked in files without first testing them locally. To avoid such a situation, we recommend that you implement a rollback mechanism that restores your SSWEs and SOWE to their status before the update. The only implication for the team in such a case is that they will continue to work with the same version as they did before the unsuccessful update. Your Working Environments Administrator can then investigate the problem and fix it without disrupting your team's development work. Of course, implementing a rollback mechanism in your updating procedure means that you will have to make a backup of your SSWEs and SOWE before starting the update.
Model for updating shared working environments
Here's how an updating and build process with a rollback mechanism might look like for your team's shared working environments:
To make it easier to update working environments, we recommend that you set up a workspace project as a root project of all other projects in a working environment. Workspace projects have two main advantages:
You should create workspace projects before you begin updating working environments for the first time. To create a workspace project for a working environment that already contains SNiFF+ projects:
Open the Working Environments tool and select the working environment for which you
want to create the workspace project.
Choose File > New Project... > with Defaults....
Select the root directory of the working environment as the project directory.
A Project Attributes dialog for a new project is opened.
Select the General node.
Give the project a name that clearly describes it (e.g.,