Cloud 66 Deployment

This page documents deployments using the next major version dpl v2, which currently is in a beta release phase. Please see our blog post for details. The current default version is dpl v1. Check dpl v1 documentation here.

Be sure to read the v2 deployment overview.

Travis CI can automatically deploy your Cloud 66 application after a successful build.

For a minimal configuration, add the following to your .travis.yml:

  provider: cloud66
  redeployment_hook: <encrypted redeployment_hook>
  edge: true # opt in to dpl v2

You can find the redeployment hook URL in the information menu within the Cloud 66 portal.

Status #

Support for deployments to Cloud66 is in alpha. Please see Maturity Levels for details.

Known options #

Use the following options to further configure the deployment.

redeployment_hook The redeployment hook URL — required, secret, type: string

Shared options #

cleanup Clean up build artifacts from the Git working directory before the deployment — type: boolean
run Commands to execute after the deployment finished successfully — type: string or array of strings

Environment variables #

All options can be given as environment variables if prefixed with CLOUD66_.

For example, redeployment_hook can be given as CLOUD66_REDEPLOYMENT_HOOK=<redeployment_hook>.

Securing secrets #

Secret option values should be given as either encrypted strings in your build configuration (.travis.yml file) or environment variables in your repository settings.

Environment variables can be set on the settings page of your repository, or using travis env set:

travis env set CLOUD66_REDEPLOYMENT_HOOK <redeployment_hook>

In order to encrypt option values when adding them to your .travis.yml file use travis encrypt:

travis encrypt <redeployment_hook>

Or use --add to directly add it to your .travis.yml file. Note that this command has to be run in your repository’s root directory:

travis encrypt --add deploy.redeployment_hook <redeployment_hook>

Pull Requests #

Note that pull request builds skip the deployment step altogether.

See also #