Deployment

The helium-cli builds are essentially built around Git tags. Thus, the deployments simply deploy an artifact of a tag (served up by GitHub). This also means you can technically deploy branches and commit hashes, for instance to a dev or stage environment, prior to actually tagging a build.

The deployment command can be viewed by executing helium-cli deploy-build help, and we see it takes <version> <env> as arguments. So, for example, executing helium-cli deploy-build 0.1.0 qa --code would deploy the 0.1.0 tag to QA, but only role actions tagged with code in Ansible. Git branches can also be deployed like helium-cli deploy-build feature-27-branch prod.

On deployment, the Ansible playbook name <env>.yml will be run. Every project role within this playbook will be deployed, but this can be filtered to only deploy certain projects using the --role.