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:
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.
Full deployment
A full deployment copies all assets from the asset management server to a target site. A full deployment comprises two steps:
All assets are deleted from the target site.
All assets from projects that are currently and previously deployed to the target site are written to that site.
Note: A full deployment to a one-off target only includes assets from checked-in projects. Assets from deployed but still-active projects are excluded from the deployment.
On a site with many assets, full deployments can be time consuming and resource intensive. Initiate a full deployment in order to refresh all site assets, especially when they are modified directly or are corrupt.
You can limit the scope of a full deployment in two ways:
The SelectiveDeleteVFSService lets you specify which file assets to delete from the local file system during full deployment. You can use this VFS in order to limit the scope of full deployment to JSP files only, and protect other file asset types from deletion.
An item descriptor’s
deployableattribute can be set to false in order to exclude specific repository item types from deployment:<attribute name=deployable value="false"/>This attribute setting must be consistent in the versioned and target site repositories; otherwise, attempts to deploy assets of this type fail.
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 few site assets changed since the previous deployment.
