Application code on the VIP Platform can only be modified using a version-controlled GitHub development workflow. There is no SFTP access to an application’s code or other related assets. GitHub repositories for VIP Platform applications are supplied by VIP.
Each VIP Platform environment tracks a specific branch of a GitHub repository. For example, the production environment will track the
master branch. Additional child environments will each have their own specific branch they are tracking.
For the production environment, the
master branch may be enabled with a GitHub Pull Request workflow which incorporates a review stage on pull requests. Merged pull requests and direct pushes are then deployed.
Commits made to a branch that deploys to a non-production environment will always auto-deploy.
Deployment typically takes two to five minutes, but this time can vary depending on the size of a codebase and any additional Continuous Integration (CI) tasks that are configured for an environment.
Build and deploy
Code that is committed to an environment’s deploy branch should contain all needed assets. On deploy, no additional building is done except for submodule includes. When using composer, for example, code should be committed to a branch only after running
composer install. An alternative to this is to set up an automated build and deploy method.
For branches already set up with automated build and deploy (
-built branches), merged changes to a
master branch, for example, will first be built in Travis or CircleCI and then pushed directly from there to the
master-built branch. The build code will then be deployed automatically.