Deployment Scope & Difference Between Full Deployment and Incremental Deployment in BCC : ATG

Deployment Scope

The scope of asset deployment to a target site is determined by the type of deployment that you choose.

Two deployment type options are available:

1. Full Deployment

2. Incremental Deployment

Your decision to perform a full or incremental deployment can depend on various factors, such as the number and type of assets to deploy, the frequency of deployment, and the reason for deployment.

Difference Between Full Deployment & Incremental Deployment:

Full Deployment

A full deployment comprises two steps:

1. All assets are deleted from the target site.

2. All changed assets from the deployed project, and all appropriate existing assets, are deployed to the site.

Full deployments can be time consuming and resource intensive if the site has a large number of assets. However, it is especially useful (and sometimes necessary) to refresh assets when they are modified directly or are corrupt. It is also practical for small sites with few assets, as it can be performed relatively quickly.



Note: You can configure a full deployment to delete only certain file assets from a VFS with the SelectiveDeleteVFSService. This VFS lets you indicate explicitly which files to delete from the local file system during deployment.

Incremental Deployment

An incremental deployment only updates the site with asset changes from the deployed projects; these changes include add, update, and/or remove operations. This type of deployment is more efficient than a full deployment, especially when very few site assets changed since the previous deployment.