Export (0) Print
Expand All

Chapter 6 - Deploying the Migrated Build System

On This Page

Introduction and Goals Introduction and Goals
Virtual Team Scenario Virtual Team Scenario
Distinct Entity Scenario Distinct Entity Scenario

Introduction and Goals

During this final phase, the team's clear goal is to place the build system into a production environment. The team must obtain approval from those who are going to use the new solution. After the build system is installed in the new environment and used successfully, the new users can sign off to signify the end of the fifth and final major project milestone: Deployment Complete.

The major task breakdown for meeting this goal is as follows:

  • Complete deployment preparations.

  • Stabilize the deployment.

  • Transfer ownership.

These are handled differently in each of the scenarios mentioned earlier.

Virtual Team Scenario

In this case, there is little or no deployment issue. The application developers have installed the migrated build system because they have been migrating the makefiles. Most of the actions in this phase are meant to provide convenient installation for developers transferring to this project or taking it up later.

The major tasks in this scenario are:

  • Ensure that a final installation package exists.

  • Ensure that documentation exists that describes installation, setup, and use of the build system and of the UNIX portability environment, if used.

  • Ensure that all developers are using the same (most recent) version.

There is no formal sign-off or acceptance in this scenario.

Distinct Entity Scenario

Deployment is more formal and gradual. It is carried out according to the deployment plan created earlier. The major tasks in this scenario are:

  • Ensure that the final installation package or packages are assembled and recorded.

  • Ensure that the documentation exists that describes:

    • How the solution will be distributed and installed by the different teams of developers.

    • How to obtain, install, and customize any UNIX portability environment used.

    • How to use the solution properly, including differences between this process and the process previously used.

    • The problems each team may encounter using the new environment and solutions to these problems.

  • Provide assistance to the application migration team as they set up the build system.

  • Obtain formal acceptance.

After the teams have accepted the build system, the build migration project may be closed, or it may be kept in the Deploying Phase as other teams require the migrated build system.

Download

Get the Solution Guide for Migrating UNIX Build Environments

Update Notifications

Sign up to learn about updates and new releases

Feedback

Send us your comments or suggestions

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft