When you are ready to push changes from the Dev to Production environment,  you can do either a full or partial deployment, depending on your requirements. This article describes how to do both.

Overview

1. Select your deployment type. 
2. Deploy the updated Applications. 
3. Deployment summary and notifications. 

Select your deployment type

Choose a full deployment to push updates from all Workspace Applications to Prod, or a partial deployment to deploy changes for a specific Application and its dependencies.

In both types of deployments, Pigment checks for correct permissions, and ensures that no disallowed Dimensional references are made. For more information, see About Deploying Changes in Test & Deploy. 
 

Start a full T&D deployment

You perform a full deployment when you need to push changes from all Applications in your Workspace from the Dev environment to Prod.

1. On the Workspace homepage, click New Deployment.
   When you do a full deploy, the Diff screen displays information on Applications updated, removed, and created in the Workspace.
    
2. Go to the list, or Diff screen, to review details of the latest structural changes.

Start a partial T&D deployment

You perform a partial deployment when you need to push changes from a specific Application from the Dev to Prod environment.

1. Do one of the following to start deploying Application-specific changes from your Dev Workspace to Prod:

   When you do a partial deploy, the Diff screen displays the following information on the selected Application and its dependent Applications.

   • On the Workspace homepage, open your Application’s settings menu (…) and select Deploy changes.
   • On the Application homepage, click the setting menu (…), and select Deploy changes.
      
2. Go to list, or Diff screen, to review details of the latest structural changes:
   
   - Selected scope.
   This is the Application from which you triggered the partial deployment. Boards that belong to this Application can be deployed. Boards using shared Views from other Applications might add these Applications to the deployment scope if these have changes.
   - Requirements.
   These Applications have structural dependencies with the Application listed in Selected Scope. They are only displayed if structural changes were applied, and if they are used directly by the chosen Application. Boards within these Applications cannot be selected, and cannot be deployed.
    

   

    

Deploy the updated Applications

When performing either type of deployment, click Deploy X Applications, enter a small description for the deployment, then click Deploy.
The Deploy button offers you two options:

• Lock all Applications. Select this option to lock all managed Applications in your source and target environments. This is the safest way to ensure that no changes can affect the deployment.
• Lock x Applications. Select this option to lock only the deployed Applications in your source and target environments. This is more flexible, however you must use this option carefully as it can risk deployment failure.

Before deployment, Pigment runs a final check of Workspace differences and permissions. When you click Deploy, T&D rechecks the source and target environments to detect any changes made during the Review step. As a review measure, Pigment locks all Applications in the Workspace to identify any possible modifications that may have been implemented during the Review step. When all checks are complete, it then unlocks all unaffected Applications, and deploys the Applications selected for that deployment.

Deployment summary and notifications

When deployment is completed, go the Prod Workspace home page and click Deployments. This page shows all deployments, including the Members responsible, deployment dates and times, as well as the number of Applications and changes involved.

When the deployment is finished, Members on both Workspaces are notified:

• All Members with the Builder role in the Dev Workspace.
• The Member who performed the deployment in the Prod Workspace.

Related Information

• Introduction to Test & Deploy
• Considerations for Opting into Test & Deploy 
• Map Out Your Test & Deploy Environments
• What Are Structural Changes in Test & Deploy?
• Manage Data Changes in Dimension Lists
• About Deploying Changes in Test & Deploy
• Understand Test & Deploy for Pigment Features