Deploying built files without a CI service

Typically, the step to build files in a CI service is scripted by the nature of CI tasks. However, if for any reason a CI service is unavailable it is still possible to deploy built files.

1. Clone the repository.
2. Checkout the working branch with the code that needs to be built (e.g. production).
3. Run the build process (e.g. npm install).
4. Create another clone of the repository, and check out the built branch that is configured to deploy to the environment (e.g. git checkout production-built).
5. Copy changes from the development copy to the deployment copy using a tool like rsync.
6. Verify the changes. They should only include built code and not development modules and dependencies.
7. Commit and push the changes to the remote repository of the deployment branch (e.g. git push origin production-built).
8. VIP’s infrastructure will detect the changes and deploy the built code to the environment(s) configured to that branch.