Although we can achieve a fully automated pipeline from end to end, we often encounter situations that hold up the deployment of a new build due to business concerns. Consequently, we tell Travis CI to run deployment scripts only when we want to release a new version.
As we stated earlier, the deployment in this example on Travis CI is merely to write the built image back to the template to be deployed. Here, we utilize the script provider to make Travis CI run our deployment script (deployment/update-config.sh) and the script does the following:
- Locates the config repository and corresponding branch
- Updates the image tag
- Commits the updated template back
After the updated image tag is committed into the repository, the job on Travis ...
