Bluemix CloudFoundry 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.
Travis CI can automatically deploy files to IBM Bluemix after a successful build.
For a minimal configuration, add the following to your
deploy: provider: bluemixcloudfoundry username: <username> password: <encrypted password> organization: <organization> space: <space> edge: true # opt in to dpl v2
Support for deployments to Bluemix Cloud Foundry is *stable**.
Known options #
Use the following options to further configure the deployment.
||Bluemix username — required, type: string|
||Bluemix password — required, secret, type: string|
||Bluemix organization — required, type: string|
||Bluemix space — required, type: string|
||Bluemix region — type: string, default:
||Bluemix api URL — type: string|
||Application name — type: string|
||Buildpack name or Git URL — type: string|
||Path to the manifest — type: string|
||Skip SSL validation — type: boolean|
Shared options #
||Clean up build artifacts from the Git working directory before the deployment — type: boolean|
||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
password can be given as
Securing secrets #
Secret option values should be given as either encrypted strings in your build
.travis.yml file) or environment variables in your repository
Environment variables can be set on the settings page of your repository, or
travis env set:
travis env set CLOUDFOUNDRY_PASSWORD <password>
In order to encrypt option values when adding them to your
travis encrypt <password>
--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.password <password>
Pull Requests #
Note that pull request builds skip the deployment step altogether.