Code deployment
A GitHub repository within the wpcomvip GitHub organization is created for every application and a branch is configured to deploy code to each of its environments. By default, application code is developed in an application’s provided wpcomvip GitHub repository and deployed via the Default Deployment method.
The Custom Deployment method can be optionally enabled for WordPress environments. Custom Deployment allows code to be developed in a version control system outside of an application’s wpcomvip GitHub repository. The developed code can then be deployed to a VIP Platform environment with VIP-CLI or a continuous deployment method.
For all deployments made to Node.js environments or WordPress environments (with either Default Deployment or Custom Deployment methods):
- Logs for an environment’s builds and deploys can be reviewed in the VIP Dashboard.
- Deployment notifications can be configured for an application’s environments.
- A rollback to a previous commit can be performed in the Deployments panel of the VIP Dashboard for an environment.
-
GitHub repository
Every WordPress and Node.js application hosted on WordPress VIP is supplied with its own GitHub repository within the wpcomvip GitHub organization.
-
Default Deployment
The Default Deployment method deploys code from a branch of an application’s wpcomvip GitHub repository to a configured environment.
-
Custom Deployment
The Custom Deployment method enables application code to be developed in a version control system outside of an application’s wpcomvip GitHub repository.
-
Duration of time for a deployment to complete
Code deployments typically take up to 5 minutes to complete. The amount of time required to complete a code deployment can vary depending on several factors.
-
Rollbacks in the VIP Dashboard
As an alternative to reverting a pull request in GitHub, a rollback to the image of a previous deployment can be performed in the Deployments panel of the VIP Dashboard.
-
Code deployment and cache clearing
When a code deployment occurs only a select group of cache clearing events will be triggered.
Last updated: October 16, 2025