dpl 1.10.17.travis.6637.6 → 2.0.0.alpha.1

data/README.md

@@ -1,968 +1,2238 @@
-# Dpl [![Build Status](https://travis-ci.org/travis-ci/dpl.svg?branch=master)](https://travis-ci.org/travis-ci/dpl) [![Code Climate](https://codeclimate.com/github/travis-ci/dpl.png)](https://codeclimate.com/github/travis-ci/dpl) [![Gem Version](https://badge.fury.io/rb/dpl.png)](http://badge.fury.io/rb/dpl) [![Coverage Status](https://coveralls.io/repos/travis-ci/dpl/badge.svg?branch=master&service=github)](https://coveralls.io/github/travis-ci/dpl?branch=master)
+# Dpl [![Build Status](https://travis-ci.com/travis-ci/dpl.svg?branch=master)](https://travis-ci.com/travis-ci/dpl) [![Code Climate](https://codeclimate.com/github/travis-ci/dpl.png)](https://codeclimate.com/github/travis-ci/dpl) [![Coverage Status](https://coveralls.io/repos/travis-ci/dpl/badge.svg?branch=master&service=github&cache=2019-08-09_17:00)](https://coveralls.io/github/travis-ci/dpl?branch=master) [![Gem Version](https://img.shields.io/gem/v/dpl)](http://rubygems.org/gems/dpl) [![Yard Docs](http://img.shields.io/badge/yard-docs-blue.svg)](http://rubydoc.info/github/travis-ci/dpl)
 
-## Writing and Testing a New Deployment Provider and new functionality
+This version of the README documents dpl v2, the next major version of dpl.
+The REAMDE for dpl v1, the version that is currently used in production on
+Travis CI can be found [here](https://github.com/travis-ci/dpl/blob/v1/README.md).
 
-See [CONTRIBUTING.md](.github/CONTRIBUTING.md).
+Dpl is command line tool for deploying code, html, packages, or build artifacts
+to various service providers.
+
+It is tightly integrated into Travis CI's [deployment integration](https://docs.travis-ci.com/user/deployment),
+but also used, and recommended by others, such as [GitLab](https://docs.gitlab.com/ee/ci/examples/deployment/).
+
+It is maintained by Travis CI, largely community driven, and it has existed
+since 2013. If you find support your preferred deployment target missing,
+please do not hesitate to get in touch, and we'll help you [add it](#contributing-to-dpl).
+
+## Table of Contents
+
+* [Requirements](#requirements)
+* [Installation](#installation)
+* [Usage](#usage)
+* [Maturity Levels](#maturity-levels)
+* [Supported Providers](#supported-providers)
+* [Contributing to Dpl](#contributing-to-dpl)
+* [Old Issues](#old-issues)
+* [Code of Conduct](#code-of-conduct)
+* [License](#license)
+* [Credits](#credits)
+
+## Requirements
+
+Dpl requires Ruby 2.2 or later.
+
+Depending on the deployment target dpl might require additional runtimes (e.g.
+Go, Node.js, or Python) to be installed. It also might require sudo access in
+order to install a Debian package.
+
+Dpl is generally optimized for usage on Linux systems.
+
+## Installation
+
+Installation:
+
+```
+gem install dpl
+```
+
+## Usage
+
+Dpl is meant and optimized for usage in ephemeral build environments, such
+as Travis CI, or any other CI/CD pipeline.
+
+Dpl is integrated to Travis CI's build configuration and build script compilation
+tooling, so all you need to do is add the proper configuration to your `.travis.yml`
+file. Please refer to [the documentation](https://docs.travis-ci.com/user/deployment)
+for details.
+
+For usage outside of Travis CI dpl can be executed as follows. Please refer to
+the respective [providers](#supported-providers) for details.
+
+```
+dpl [provider] [options]
+```
+
+Dpl can be used locally, e.g. on your development machine, but it might leave
+artifacts that may alter the behaviour of your system. If you encounter this
+behaviour and it presents a serious issue to you then please open an
+[issue](https://github.com/travis-ci/dpl/issues/new).
+
+### Cleaning up the Git working directory
+
+Dpl v1 has cleaned up the Git working directory by default, using `git stash
+--all`. The default for this option has been changed in dpl v2, and users now
+need to opt in to cleaning up any left over artifacts from the build process
+by passing the option `--cleanup`.
+
+The status of the working directory is relevant only to providers that package
+and push it to the respective remote service (e.g. `heroku` when using the
+`api` strategy, package registry providers, etc.). Most providers will either
+push the latest Git commit, or pull code from a remote repository.
+
+## Maturity Levels
+
+In order to communicate the current development status and maturity of dpl's
+support for a particular service the respective provider is marked with one of
+the following maturity levels, according to the given criteria:
+
+* `dev` - the provider is in development (initial level)
+* `alpha` - the provider is fully tested
+* `beta` - the provider has been in alpha for at least a month, and successful real-world production deployments have been observed
+* `stable` - the provider has been in beta for at least two months, and there are no open issues that qualify as critical (such as deployments failing, documented functionality broken, etc)
+
+## Supported Providers
 
-## Supported Providers:
 Dpl supports the following providers:
 
-* [Anynines](#anynines)
-* [Atlas by HashiCorp](#atlas)
-* [AWS CodeDeploy](#aws-codedeploy)
-* [AWS Elastic Beanstalk](#elastic-beanstalk)
-* [AWS OpsWorks](#opsworks)
-* [AWS S3](#s3)
-* [Azure Web Apps](#azure-web-apps)
-* [Bintray](#bintray)
-* [BitBalloon](#bitballoon)
-* [Bluemix Cloud Foundry](#bluemix-cloud-foundry)
-* [Boxfuse](#boxfuse)
-* [cargo](#cargo)
-* [Catalyze](#catalyze)
-* [Chef Supermarket](#chef-supermarket)
-* [Cloud 66](#cloud-66)
-* [Cloud Foundry](#cloud-foundry)
-* [Deis](#deis)
-* [Engine Yard](#engine-yard)
-* [Firebase](#firebase)
-* [Github Pages](#github-pages)
-* [Github Releases](#github-releases)
-* [Google App Engine (experimental)](#google-app-engine)
-* [Google Cloud Storage](#google-cloud-storage)
-* [Hackage](#hackage)
-* [Hephy](#hephy)
-* [Heroku](#heroku)
-* [Lambda](#lambda)
-* [Launchpad](#launchpad)
-* [Nodejitsu](#nodejitsu)
-* [npm](#npm)
-* [OpenShift](#openshift)
-* [packagecloud](#packagecloud)
-* [Puppet Forge](#puppet-forge)
-* [PyPi](#pypi)
-* [Rackspace Cloud Files](#rackspace-cloud-files)
-* [RubyGems](#rubygems)
-* [Scalingo](#scalingo)
-* [Script](#script)
-* [Snap](#snap)
-* [Surge.sh](#surgesh)
-* [TestFairy](#testfairy)
-
-## Installation:
-
-Dpl is published to rubygems.
-
-* Dpl requires ruby 2.2 and later.
-* To install: `gem install dpl`
-
-## Usage:
-
-### Security Warning:
-
-Running dpl in a terminal that saves history is insecure as your password/api key will be saved as plain text by it.
-
-### Global Flags
-* `--provider=<provider>` sets the provider you want to deploy to. Every provider has slightly different flags, which are documented in the section about your provider following.
-*  Dpl will deploy by default from the latest commit. Use the `--skip_cleanup`  flag to deploy from the current file state. Note that many providers deploy by git and could ignore this option.
-
-### Heroku:
-
-#### Options:
-* **api-key**: Heroku API Key
-* **strategy**: Deployment strategy for Dpl. Defaults to `api`. The other option is `git`.
-* **app**: Heroku app name. Defaults to the name of your git repo.
-* **username**: heroku username. Not necessary if api-key is used. Requires git strategy.
-* **password**: heroku password. Not necessary if api-key is used. Requires git strategy.
-
-#### API vs Git Deploy:
-* API deploy will tar up the current directory (minus the git repo) and send it to Heroku.
-* Git deploy will send the contents of the git repo only, so may not contain any local changes.
-* The Git strategy allows using *user* and *password* instead of *api-key*.
-* When using Git, Heroku might send you an email for every deploy, as it adds a temporary SSH key to your account.
-
-#### Examples:
-
-    dpl --provider=heroku --api-key=`heroku auth:token`
-    dpl --provider=heroku --strategy=git --username=<username> --password=<password>  --app=<application>
-
-
-### Bintray:
-
-#### Options:
-
-* **file**: Path to a descriptor file, containing information for the Bintray upload.
-* **user**: Bintray user
-* **key**: Bintray API key
-* **passphrase**: Optional. In case a passphrase is configured on Bintray and GPG signing is used.
-* **dry-run**: Optional. If set to true, skips sending requests to Bintray. Useful for testing your configuration.
-
-#### Descriptor file example:
-```groovy
-{
-	/* Bintray package information.
-	   In case the package already exists on Bintray, only the name, repo and subject
-	   fields are mandatory. */
-
-	"package": {
-		"name": "auto-upload", // Bintray package name
-		"repo": "myRepo", // Bintray repository name
-		"subject": "myBintrayUser", // Bintray subject (user or organization)
-		"desc": "I was pushed completely automatically",
-		"website_url": "www.jfrog.com",
- 		"issue_tracker_url": "https://github.com/bintray/bintray-client-java/issues",
- 		"vcs_url": "https://github.com/bintray/bintray-client-java.git",
-		"github_use_tag_release_notes": true,
-		"github_release_notes_file": "RELEASE.txt",
- 		"licenses": ["MIT"],
- 		"labels": ["cool", "awesome", "gorilla"],
- 		"public_download_numbers": false,
- 		"public_stats": false,
- 		"attributes": [{"name": "att1", "values" : ["val1"], "type": "string"},
-     				   {"name": "att2", "values" : [1, 2.2, 4], "type": "number"},
-     				   {"name": "att5", "values" : ["2014-12-28T19:43:37+0100"], "type": "date"}]
- 	},
-
-	/* Package version information.
-	   In case the version already exists on Bintray, only the name fields is mandatory. */
-
-	"version": {
-		"name": "0.5",
-		"desc": "This is a version",
-		"released": "2015-01-04",
-		"vcs_tag": "0.5",
-	 	"attributes": [{"name": "VerAtt1", "values" : ["VerVal1"], "type": "string"},
-  					   {"name": "VerAtt2", "values" : [1, 3.2, 5], "type": "number"},
-					   {"name": "VerAtt3", "values" : ["2015-01-01T19:43:37+0100"], "type": "date"}],
-		"gpgSign": false
-	},
-
-	/* Configure the files you would like to upload to Bintray and their upload path.
-	You can define one or more groups of patterns.
-	Each group contains three patterns:
-
-	includePattern: Pattern in the form of Ruby regular expression, indicating the path of files to be uploaded to Bintray.
-	excludePattern: Optional. Pattern in the form of Ruby regular expression, indicating the path of files to be removed from the list of files specified by the includePattern.
-	uploadPattern: Upload path on Bintray. The path can contain symbols in the form of $1, $2,... that are replaced with capturing groups defined in the include pattern.
-
-	In the example below, the following files are uploaded,
-	1. All gem files located under build/bin/ (including sub directories),
-	except for files under a the do-not-deploy directory.
-	The files will be uploaded to Bintray under the gems folder.
-	2. All files under build/docs. The files will be uploaded to Bintray under the docs folder.
-
-	Note: Regular expressions defined as part of the includePattern property must be wrapped with brackets. */
-
-	"files":
-		[
-		{"includePattern": "build/bin(.*)*/(.*\.gem)", "excludePattern": ".*/do-not-deploy/.*", "uploadPattern": "gems/$2"},
-		{"includePattern": "build/docs/(.*)", "uploadPattern": "docs/$1"}
-		],
-	"publish": true
-}
-```
-
-#### Debian Upload
-
-When artifacts are uploaded to a Debian repository using the Automatic index layout, the Debian distribution information is required and must be specified. The information is specified in the descriptor file by the matrixParams as part of the files closure as shown in the following example:
-```groovy
-    "files":
-        [{"includePattern": "build/bin/(.*\.deb)", "uploadPattern": "$1",
-		"matrixParams": {
-			"deb_distribution": "vivid",
-			"deb_component": "main",
-			"deb_architecture": "amd64"}
-		}
-	]
-```
-
-#### Examples:
-    dpl --provider=bintray --file=<path> --user=<username> --key=<api-key>
-    dpl --provider=bintray --file=<path> --user=<username> --key=<api-key> --passphrase=<passphrase>
+  * [Anynines](#anynines)
+  * [Atlas](#atlas)
+  * [AWS Code Deploy](#aws-code-deploy)
+  * [AWS Elastic Beanstalk](#aws-elastic-beanstalk)
+  * [AWS Lambda](#aws-lambda)
+  * [AWS OpsWorks](#aws-opsworks)
+  * [AWS S3](#aws-s3)
+  * [Azure Web Apps](#azure-web-apps)
+  * [Bintray](#bintray)
+  * [Bluemix Cloud Foundry](#bluemix-cloud-foundry)
+  * [Boxfuse](#boxfuse)
+  * [Cargo](#cargo)
+  * [Chef Supermarket](#chef-supermarket)
+  * [Cloud Files](#cloud-files)
+  * [Cloud Foundry](#cloud-foundry)
+  * [Cloud66](#cloud66)
+  * [Datica](#datica)
+  * [Engineyard](#engineyard)
+  * [Firebase](#firebase)
+  * [GitHub Pages](#github-pages)
+  * [GitHub Releases](#github-releases)
+  * [Google App Engine](#google-app-engine)
+  * [Google Cloud Store](#google-cloud-store)
+  * [Hackage](#hackage)
+  * [Hephy](#hephy)
+  * [Heroku API](#heroku-api)
+  * [Heroku Git](#heroku-git)
+  * [Launchpad](#launchpad)
+  * [Netlify](#netlify)
+  * [npm](#npm)
+  * [OpenShift](#openshift)
+  * [Packagecloud](#packagecloud)
+  * [Puppet Forge](#puppet-forge)
+  * [PyPI](#pypi)
+  * [Rubygems](#rubygems)
+  * [Scalingo](#scalingo)
+  * [Script](#script)
+  * [Snap](#snap)
+  * [Surge](#surge)
+  * [TestFairy](#testfairy)
+  * [Transifex](#transifex)
+
+
+### Anynines
+
+```
+Usage: dpl anynines [options]
+
+Summary:
+
+  Anynines deployment provider
+
+Description:
+
+  tbd
+
+  Support for deployments to Anynines is in alpha. Please see here: https://github.com/travis-ci/dpl/#maturity-levels
+
+Options:
+
+  --username USER         anynines username (type: string, required: true)
+  --password PASS         anynines password (type: string, required: true)
+  --organization ORG      anynines target organization (type: string, required: true)
+  --space SPACE           anynines target space (type: string, required: true)
+  --app_name APP          Application name (type: string)
+  --buildpack PACK        Custom buildpack name or Git URL (type: string)
+  --manifest FILE         Path to the manifest (type: string)
+
+Common Options:
+
+  --run CMD               Command to execute after the deployment finished successfully (type: array
+                          (string, can be given multiple times))
+  --[no-]cleanup          Skip cleaning up build artifacts before the deployment
+  --help                  Get help on this command
+
+Examples:
+
+  dpl anynines --username user --password pass --organization org --space space
+  dpl anynines --username user --password pass --organization org --space space --app_name app
+```
+
+### Atlas
+
+```
+Usage: dpl atlas [options]
+
+Summary:
+
+  Atlas deployment provider
+
+Description:
+
+  tbd
+
+  Support for deployments to Atlas is in alpha. Please see here: https://github.com/travis-ci/dpl/#maturity-levels
+
+Options:
+
+  --app APP            The Atlas application to upload to (type: string, required: true)
+  --token TOKEN        The Atlas API token (type: string, required: true)
+  --paths PATH         Files or directories to upload (type: array (string, can be given multiple
+                       times), default: ["."])
+  --address ADDR       The address of the Atlas server (type: string)
+  --include GLOB       Glob pattern of files or directories to include (type: array (string, can be
+                       given multiple times))
+  --exclude GLOB       Glob pattern of files or directories to exclude (type: array (string, can be
+                       given multiple times))
+  --metadata DATA      Arbitrary key=value (string) metadata to be sent with the upload (type: array
+                       (string, can be given multiple times))
+  --[no-]vcs           Get lists of files to exclude and include from a VCS (Git, Mercurial or SVN)
+  --args ARGS          Args to pass to the atlas-upload CLI (type: string)
+  --[no-]debug         Turn on debug output
+
+Common Options:
+
+  --run CMD            Command to execute after the deployment finished successfully (type: array
+                       (string, can be given multiple times))
+  --[no-]cleanup       Skip cleaning up build artifacts before the deployment
+  --help               Get help on this command
+
+Examples:
+
+  dpl atlas --app app --token token
+  dpl atlas --app app --token token --paths path --address addr --include glob
+```
+
+### AWS Code Deploy
+
+```
+Usage: dpl codedeploy [options]
+
+Summary:
+
+  AWS Code Deploy deployment provider
+
+Description:
+
+  tbd
 
+  Support for deployments to AWS Code Deploy is in alpha. Please see here: https://github.com/travis-ci/dpl/#maturity-levels
+
+Options:
+
+  --access_key_id ID              AWS access key (type: string, required: true)
+  --secret_access_key KEY         AWS secret access key (type: string, required: true)
+  --application NAME              CodeDeploy application name (type: string, required: true)
+  --deployment_group GROUP        CodeDeploy deployment group name (type: string)
+  --revision_type TYPE            CodeDeploy revision type (type: string, known values: s3, github, downcase:
+                                  true)
+  --commit_id SHA                 Commit ID in case of GitHub (type: string)
+  --repository NAME               Repository name in case of GitHub (type: string)
+  --bucket NAME                   S3 bucket in case of S3 (type: string)
+  --region REGION                 AWS availability zone (type: string, default: us-east-1)
+  --file_exists_behavior STR      How to handle files that already exist in a deployment target location (type:
+                                  string, default: disallow, known values: disallow, overwrite, retain)
+  --[no-]wait_until_deployed      Wait until the deployment has finished
+  --bundle_type TYPE              type: string
+  --endpoint ENDPOINT             type: string
+  --key KEY                       type: string
+  --description DESCR             type: string
+
+Common Options:
+
+  --run CMD                       Command to execute after the deployment finished successfully (type: array
+                                  (string, can be given multiple times))
+  --[no-]cleanup                  Skip cleaning up build artifacts before the deployment
+  --help                          Get help on this command
+
+Examples:
+
+  dpl codedeploy --access_key_id id --secret_access_key key --application name
+  dpl codedeploy --access_key_id id --secret_access_key key --application name --deployment_group group --revision_type s3
+```
+
+### AWS Elastic Beanstalk
+
+```
+Usage: dpl elasticbeanstalk [options]
+
+Summary:
+
+  AWS Elastic Beanstalk deployment provider
+
+Description:
+
+  tbd
+
+  Support for deployments to AWS Elastic Beanstalk is in alpha. Please see here: https://github.com/travis-ci/dpl/#maturity-levels
+
+Options:
+
+  --access_key_id ID                  AWS Access Key ID (type: string, required: true)
+  --secret_access_key KEY             AWS Secret Key (type: string, required: true)
+  --region REGION                     AWS Region the Elastic Beanstalk app is running in (type: string, default:
+                                      us-east-1)
+  --app NAME                          Elastic Beanstalk application name (type: string, default: repo name)
+  --env NAME                          Elastic Beanstalk environment name which will be updated (type: string,
+                                      required: true)
+  --bucket NAME                       Bucket name to upload app to (type: string, required: true, alias: bucket_name)
+  --bucket_path PATH                  Location within Bucket to upload app to (type: string)
+  --description DESC                  Description for the application version (type: string)
+  --label LABEL                       Label for the application version (type: string)
+  --zip_file PATH                     The zip file that you want to deploy (type: string)
+  --[no-]only_create_app_version      Only create the app version, do not actually deploy it
+  --[no-]wait_until_deployed          Wait until the deployment has finished
+
+Common Options:
+
+  --run CMD                           Command to execute after the deployment finished successfully (type: array
+                                      (string, can be given multiple times))
+  --[no-]cleanup                      Skip cleaning up build artifacts before the deployment
+  --help                              Get help on this command
+
+Examples:
+
+  dpl elasticbeanstalk --access_key_id id --secret_access_key key --env name --bucket name
+  dpl elasticbeanstalk --access_key_id id --secret_access_key key --env name --bucket name --region region
+```
+
+### AWS Lambda
+
+```
+Usage: dpl lambda [options]
+
+Summary:
+
+  AWS Lambda deployment provider
+
+Description:
+
+  tbd
+
+  Support for deployments to AWS Lambda is in alpha. Please see here: https://github.com/travis-ci/dpl/#maturity-levels
+
+Options:
+
+  --access_key_id ID            AWS access key id (type: string, required: true)
+  --secret_access_key KEY       AWS secret key (type: string, required: true)
+  --region REGION               AWS region the Lambda function is running in (type: string, default: us-east-1)
+  --function_name FUNC          Name of the Lambda being created or updated (type: string, required: true)
+  --role ROLE                   ARN of the IAM role to assign to the Lambda function (type: string, note:
+                                required for creating a new function)
+  --handler_name NAME           Function the Lambda calls to begin execution. (type: string, note: required for
+                                creating a new function)
+  --module_name NAME            Name of the module that exports the handler (type: string, requires:
+                                handler_name, default: index)
+  --description DESCR           Description of the Lambda being created or updated (type: string)
+  --timeout SECS                Function execution time (in seconds) at which Lambda should terminate the
+                                function (type: string, default: 3)
+  --memory_size MB              Amount of memory in MB to allocate to this Lambda (type: string, default: 128)
+  --subnet_ids IDS              List of subnet IDs to be added to the function (type: array (string, can be
+                                given multiple times), note: Needs the ec2:DescribeSubnets and ec2:DescribeVpcs
+                                permission for the user of the access/secret key to work)
+  --security_group_ids IDS      List of security group IDs to be added to the function (type: array (string, can
+                                be given multiple times), note: Needs the ec2:DescribeSecurityGroups and
+                                ec2:DescribeVpcs permission for the user of the access/secret key to work)
+  --environment VARS            List of Environment Variables to add to the function (type: array (string, can
+                                be given multiple times), alias: environment_variables, format: /[\w\-]+=.+/,
+                                note: Can be encrypted for added security)
+  --runtime NAME                Lambda runtime to use (type: string, default: nodejs8.10, known values: java8,
+                                nodejs8.10, nodejs10.x, python2.7, python3.6, python3.7, dotnetcore2.1, go1.x,
+                                ruby2.5)
+  --dead_letter_arn ARN         ARN to an SNS or SQS resource used for the dead letter queue. (type: string)
+  --kms_key_arn ARN             KMS key ARN to use to encrypt environment_variables. (type: string)
+  --tracing_mode MODE           Tracing mode (type: string, default: PassThrough, known values: Active,
+                                PassThrough, note: Needs xray:PutTraceSegments xray:PutTelemetryRecords on the
+                                role)
+  --layers LAYERS               Function layer arns (type: array (string, can be given multiple times))
+  --function_tags TAGS          List of tags to add to the function (type: array (string, can be given multiple
+                                times), format: /[\w\-]+=.+/, note: Can be encrypted for added security)
+  --[no-]publish                Create a new version of the code instead of replacing the existing one.
+  --zip PATH                    Path to a packaged Lambda, a directory to package, or a single file to package
+                                (type: string, default: .)
+  --[no-]dot_match              Include hidden .* files to the zipped archive
+
+Common Options:
+
+  --run CMD                     Command to execute after the deployment finished successfully (type: array
+                                (string, can be given multiple times))
+  --[no-]cleanup                Skip cleaning up build artifacts before the deployment
+  --help                        Get help on this command
+
+Examples:
+
+  dpl lambda --access_key_id id --secret_access_key key --function_name func
+  dpl lambda --access_key_id id --secret_access_key key --function_name func --region region --role role
+```
+
+### AWS OpsWorks
+
+```
+Usage: dpl opsworks [options]
+
+Summary:
+
+  AWS OpsWorks deployment provider
+
+Description:
+
+  tbd
+
+  Support for deployments to AWS OpsWorks is in alpha. Please see here: https://github.com/travis-ci/dpl/#maturity-levels
+
+Options:
+
+  --access_key_id ID              AWS access key id (type: string, required: true)
+  --secret_access_key KEY         AWS secret key (type: string, required: true)
+  --app_id APP                    The app id (type: string, required: true)
+  --region REGION                 AWS region (type: string, default: us-east-1)
+  --instance_ids ID               An instance id (type: array (string, can be given multiple times))
+  --layer_ids ID                  A layer id (type: array (string, can be given multiple times))
+  --[no-]migrate                  Migrate the database.
+  --[no-]wait_until_deployed      Wait until the app is deployed and return the deployment status.
+  --[no-]update_on_success        When wait-until-deployed and updated-on-success are both not given, application
+                                  source is updated to the current SHA. Ignored when wait-until-deployed is not
+                                  given. (alias: update_app_on_success)
+  --custom_json JSON              Custom json options override (overwrites default configuration) (type: string)
+
+Common Options:
+
+  --run CMD                       Command to execute after the deployment finished successfully (type: array
+                                  (string, can be given multiple times))
+  --[no-]cleanup                  Skip cleaning up build artifacts before the deployment
+  --help                          Get help on this command
+
+Examples:
+
+  dpl opsworks --access_key_id id --secret_access_key key --app_id app
+  dpl opsworks --access_key_id id --secret_access_key key --app_id app --region region --instance_ids id
+```
+
+### AWS S3
+
+```
+Usage: dpl s3 [options]
+
+Summary:
+
+  AWS S3 deployment provider
+
+Description:
+
+  tbd
+
+  Support for deployments to AWS S3 is in alpha. Please see here: https://github.com/travis-ci/dpl/#maturity-levels
+
+Options:
+
+  --access_key_id ID                  AWS access key id (type: string, required: true)
+  --secret_access_key KEY             AWS secret key (type: string, required: true)
+  --bucket BUCKET                     S3 bucket (type: string, required: true)
+  --region REGION                     S3 region (type: string, default: us-east-1)
+  --endpoint URL                      S3 endpoint (type: string)
+  --upload_dir DIR                    S3 directory to upload to (type: string)
+  --storage_class CLASS               S3 storage class to upload as (type: string, default: STANDARD, known values:
+                                      STANDARD, STANDARD_IA, REDUCED_REDUNDANCY)
+  --[no-]server_side_encryption       Use S3 Server Side Encryption (SSE-AES256)
+  --local_dir DIR                     Local directory to upload from (type: string, default: ., e.g.: ~/travis/build
+                                      (absolute path) or ./build (relative path))
+  --[no-]detect_encoding              HTTP header Content-Encoding for files compressed with gzip and compress
+                                      utilities
+  --cache_control STR                 HTTP header Cache-Control to suggest that the browser cache the file (type:
+                                      array (string, can be given multiple times), default: no-cache, known values:
+                                      /^no-cache.*/, /^no-store.*/, /^max-age=\d+.*/, /^s-maxage=\d+.*/,
+                                      /^no-transform/, /^public/, /^private/, note: accepts mapping values to globs)
+  --expires DATE                      Date and time that the cached object expires (type: array (string, can be given
+                                      multiple times), format: /^"?\d{4}-\d{2}-\d{2} \d{2}:\d{2}:\d{2} .+"?.*$/, note:
+                                      accepts mapping values to globs)
+  --acl ACL                           Access control for the uploaded objects (type: string, default: private, known
+                                      values: private, public_read, public_read_write, authenticated_read,
+                                      bucket_owner_read, bucket_owner_full_control)
+  --[no-]dot_match                    Upload hidden files starting with a dot
+  --index_document_suffix SUFFIX      Index document suffix of a S3 website (type: string)
+  --default_text_charset CHARSET      Default character set to append to the content-type of text files (type: string)
+  --max_threads NUM                   The number of threads to use for S3 file uploads (type: integer, default: 5,
+                                      max: 15)
+  --[no-]overwrite                    Whether or not to overwrite existing files (default: true)
+  --[no-]verbose                      Be verbose about uploading files
+
+Common Options:
+
+  --run CMD                           Command to execute after the deployment finished successfully (type: array
+                                      (string, can be given multiple times))
+  --[no-]cleanup                      Skip cleaning up build artifacts before the deployment
+  --help                              Get help on this command
+
+Examples:
+
+  dpl s3 --access_key_id id --secret_access_key key --bucket bucket
+  dpl s3 --access_key_id id --secret_access_key key --bucket bucket --region region --endpoint url
+```
+
+### Azure Web Apps
+
+```
+Usage: dpl azure_web_apps [options]
+
+Summary:
+
+  Azure Web Apps deployment provider
+
+Description:
+
+  tbd
+
+  Support for deployments to Azure Web Apps is in alpha. Please see here: https://github.com/travis-ci/dpl/#maturity-levels
+
+Options:
+
+  --site SITE          Web App name (e.g. myapp in myapp.azurewebsites.net) (type: string, required:
+                       true)
+  --username NAME      Web App Deployment Username (type: string, required: true)
+  --password PASS      Web App Deployment Password (type: string, required: true)
+  --slot SLOT          Slot name (if your app uses staging deployment) (type: string)
+  --[no-]verbose       Print deployment output from Azure. Warning: If authentication fails, Git prints
+                       credentials in clear text. Correct credentials remain hidden.
+
+Common Options:
+
+  --run CMD            Command to execute after the deployment finished successfully (type: array
+                       (string, can be given multiple times))
+  --[no-]cleanup       Skip cleaning up build artifacts before the deployment
+  --help               Get help on this command
+
+Examples:
+
+  dpl azure_web_apps --site site --username name --password pass
+  dpl azure_web_apps --site site --username name --password pass --slot slot --verbose
+```
+
+### Bintray
+
+```
+Usage: dpl bintray [options]
+
+Summary:
+
+  Bintray deployment provider
+
+Description:
+
+  tbd
+
+  Support for deployments to Bintray is in alpha. Please see here: https://github.com/travis-ci/dpl/#maturity-levels
+
+Options:
+
+  --user USER              Bintray user (type: string, required: true)
+  --key KEY                Bintray API key (type: string, required: true)
+  --file FILE              Path to a descriptor file for the Bintray upload (type: string, required: true)
+  --passphrase PHRASE      Passphrase as configured on Bintray (if GPG signing is used) (type: string)
+
+Common Options:
+
+  --run CMD                Command to execute after the deployment finished successfully (type: array
+                           (string, can be given multiple times))
+  --[no-]cleanup           Skip cleaning up build artifacts before the deployment
+  --help                   Get help on this command
+
+Examples:
+
+  dpl bintray --user user --key key --file file
+  dpl bintray --user user --key key --file file --passphrase phrase --run cmd
+```
+
+### Bluemix Cloud Foundry
+
+```
+Usage: dpl bluemixcloudfoundry [options]
+
+Summary:
+
+  Bluemix Cloud Foundry deployment provider
+
+Description:
+
+  tbd
+
+  Support for deployments to Bluemix Cloud Foundry is in alpha. Please see here: https://github.com/travis-ci/dpl/#maturity-levels
+
+Options:
+
+  --username USER                 Bluemix username (type: string, required: true)
+  --password PASS                 Bluemix password (type: string, required: true)
+  --organization ORG              Bluemix target organization (type: string, required: true)
+  --space SPACE                   Bluemix target space (type: string, required: true)
+  --region REGION                 Bluemix region (type: string, default: ng, known values: ng, eu-gb, eu-de,
+                                  au-syd)
+  --api URL                       Bluemix api URL (type: string)
+  --app_name APP                  Application name (type: string)
+  --buildpack PACK                Custom buildpack name or Git URL (type: string)
+  --manifest FILE                 Path to the manifest (type: string)
+  --[no-]skip_ssl_validation      Skip SSL validation
+
+Common Options:
+
+  --run CMD                       Command to execute after the deployment finished successfully (type: array
+                                  (string, can be given multiple times))
+  --[no-]cleanup                  Skip cleaning up build artifacts before the deployment
+  --help                          Get help on this command
+
+Examples:
+
+  dpl bluemixcloudfoundry --username user --password pass --organization org --space space
+  dpl bluemixcloudfoundry --username user --password pass --organization org --space space --region ng
+```
 
 ### Boxfuse
 
-Boxfuse will transform your .jar or .war file of your JVM-based application into a minimal machine image based upon which it will launch EC2 instances on AWS.
+```
+Usage: dpl boxfuse [options]
+
+Summary:
+
+  Boxfuse deployment provider
+
+Description:
+
+  tbd
+
+  Support for deployments to Boxfuse is in alpha. Please see here: https://github.com/travis-ci/dpl/#maturity-levels
+
+Options:
+
+  --user USER             type: string, required: true
+  --secret SECRET         type: string, required: true
+  --config_file FILE      type: string, alias: configfile (deprecated, please use config_file)
+  --payload PAYLOAD       type: string
+  --app APP               type: string
+  --version VERSION       type: string
+  --env ENV               type: string
+  --extra_args ARGS       type: string
+
+Common Options:
+
+  --run CMD               Command to execute after the deployment finished successfully (type: array
+                          (string, can be given multiple times))
+  --[no-]cleanup          Skip cleaning up build artifacts before the deployment
+  --help                  Get help on this command
+
+Examples:
+
+  dpl boxfuse --user user --secret secret
+  dpl boxfuse --user user --secret secret --config_file file --payload payload --app app
+```
+
+### Cargo
+
+```
+Usage: dpl cargo [options]
+
+Summary:
+
+  Cargo deployment provider
+
+Description:
+
+  tbd
+
+  Support for deployments to Cargo is in alpha. Please see here: https://github.com/travis-ci/dpl/#maturity-levels
+
+Options:
+
+  --token TOKEN       Cargo registry API token (type: string, required: true)
+
+Common Options:
+
+  --run CMD           Command to execute after the deployment finished successfully (type: array
+                      (string, can be given multiple times))
+  --[no-]cleanup      Skip cleaning up build artifacts before the deployment
+  --help              Get help on this command
+
+Examples:
+
+  dpl cargo --token token
+  dpl cargo --token token --run cmd --cleanup
+```
+
+### Chef Supermarket
+
+```
+Usage: dpl chef_supermarket [options]
+
+Summary:
+
+  Chef Supermarket deployment provider
+
+Description:
+
+  tbd
+
+  Support for deployments to Chef Supermarket is in alpha. Please see here: https://github.com/travis-ci/dpl/#maturity-levels
+
+Options:
+
+  --user_id ID          Chef Supermarket user name (type: string, required: true)
+  --client_key KEY      Client API key file name (type: string, required: true)
+  --name NAME           Cookbook name (type: string, alias: cookbook_name, note: defaults to the name
+                        given in metadata.json or metadata.rb)
+  --category CAT        Cookbook category in Supermarket (type: string, required: true, alias:
+                        cookbook_category, see: https://docs.getchef.com/knife_cookbook_site.html#id12)
+  --dir DIR             Directory containing the cookbook (type: string, default: .)
+
+Common Options:
+
+  --run CMD             Command to execute after the deployment finished successfully (type: array
+                        (string, can be given multiple times))
+  --[no-]cleanup        Skip cleaning up build artifacts before the deployment
+  --help                Get help on this command
+
+Examples:
+
+  dpl chef_supermarket --user_id id --client_key key --category cat
+  dpl chef_supermarket --user_id id --client_key key --category cat --name name --dir dir
+```
+
+### Cloud Files
+
+```
+Usage: dpl cloudfiles [options]
+
+Summary:
+
+  Cloud Files deployment provider
+
+Description:
+
+  tbd
+
+  Support for deployments to Cloud Files is in alpha. Please see here: https://github.com/travis-ci/dpl/#maturity-levels
+
+Options:
+
+  --username USER       Rackspace username (type: string, required: true)
+  --api_key KEY         Rackspace API key (type: string, required: true)
+  --region REGION       Cloudfiles region (type: string, required: true, known values: ord, dfw, syd,
+                        iad, hkg)
+  --container NAME      Name of the container that files will be uploaded to (type: string, required:
+                        true)
+  --glob GLOB           Paths to upload (type: string, default: **/*)
+  --[no-]dot_match      Upload hidden files starting a dot
+
+Common Options:
+
+  --run CMD             Command to execute after the deployment finished successfully (type: array
+                        (string, can be given multiple times))
+  --[no-]cleanup        Skip cleaning up build artifacts before the deployment
+  --help                Get help on this command
+
+Examples:
+
+  dpl cloudfiles --username user --api_key key --region ord --container name
+  dpl cloudfiles --username user --api_key key --region ord --container name --glob glob
+```
+
+### Cloud Foundry
+
+```
+Usage: dpl cloudfoundry [options]
+
+Summary:
+
+  Cloud Foundry deployment provider
+
+Description:
+
+  tbd
+
+  Support for deployments to Cloud Foundry is in alpha. Please see here: https://github.com/travis-ci/dpl/#maturity-levels
+
+Options:
+
+  --username USER                 Cloud Foundry username (type: string, required: true)
+  --password PASS                 Cloud Foundry password (type: string, required: true)
+  --organization ORG              Cloud Foundry target organization (type: string, required: true)
+  --space SPACE                   Cloud Foundry target space (type: string, required: true)
+  --api URL                       Cloud Foundry api URL (type: string, required: true)
+  --app_name APP                  Application name (type: string)
+  --buildpack PACK                Custom buildpack name or Git URL (type: string)
+  --manifest FILE                 Path to the manifest (type: string)
+  --[no-]skip_ssl_validation      Skip SSL validation
+  --[no-]v3                       Use the v3 API version to push the application
+
+Common Options:
+
+  --run CMD                       Command to execute after the deployment finished successfully (type: array
+                                  (string, can be given multiple times))
+  --[no-]cleanup                  Skip cleaning up build artifacts before the deployment
+  --help                          Get help on this command
+
+Examples:
+
+  dpl cloudfoundry --username user --password pass --organization org --space space --api url
+```
+
+### Cloud66
+
+```
+Usage: dpl cloud66 [options]
+
+Summary:
+
+  Cloud66 deployment provider
+
+Description:
+
+  tbd
+
+  Support for deployments to Cloud66 is in alpha. Please see here: https://github.com/travis-ci/dpl/#maturity-levels
+
+Options:
+
+  --redeployment_hook URL      The redeployment hook URL (type: string, required: true)
+
+Common Options:
+
+  --run CMD                    Command to execute after the deployment finished successfully (type: array
+                               (string, can be given multiple times))
+  --[no-]cleanup               Skip cleaning up build artifacts before the deployment
+  --help                       Get help on this command
+
+Examples:
+
+  dpl cloud66 --redeployment_hook url
+  dpl cloud66 --redeployment_hook url --run cmd --cleanup
+```
+
+### Datica
+
+```
+Usage: dpl datica [options]
+
+Summary:
+
+  Datica deployment provider
+
+Description:
+
+  tbd
+
+  Support for deployments to Datica is in development. Please see here: https://github.com/travis-ci/dpl/#maturity-levels
+
+Options:
+
+  --target TARGET      The git remote repository to deploy to (type: string, required: true)
+  --path PATH          Path to files to deploy (type: string, default: .)
+
+Common Options:
 
-#### Options
+  --run CMD            Command to execute after the deployment finished successfully (type: array
+                       (string, can be given multiple times))
+  --[no-]cleanup       Skip cleaning up build artifacts before the deployment
+  --help               Get help on this command
 
-* **user**: Your Boxfuse user
-* **secret**: Your Boxfuse secret
-* **configfile**: The Boxfuse configuration file to use (default: boxfuse.conf)
-* **payload**: The file to use as a payload for the image
-* **app**: The Boxfuse app to deploy (default: auto-detected based on payload file name)
-* **version**: The version to assign to the image (default: auto-detected based on payload file name)
-* **env**: The Boxfuse environment to deploy to (default: test)
+Examples:
 
-All options can also be configured directly in boxfuse.conf as described in [the documentation](https://boxfuse.com/docs/commandline/#configuration).
+  dpl datica --target target
+  dpl datica --target target --path path --run cmd --cleanup
+```
+
+### Engineyard
+
+```
+Usage: dpl engineyard [options]
 
-#### Environment Variables
+Summary:
 
-For authentication you can also use Travis CI secure environment variable:
+  Engineyard deployment provider
 
-* **BOXFUSE_USER**: Your Boxfuse user
-* **BOXFUSE_SECRET**: Your Boxfuse secret
+Description:
 
-#### Examples
-    dpl --provider=boxfuse
-    dpl --provider=boxfuse --user=<your-boxfuse-user> --secret=<your-boxfuse-secret> --env=<your-boxfuse-environment>
-    dpl --provider=boxfuse --configfile=<your-boxfuse-config-file>
+  tbd
 
+  Support for deployments to Engineyard is in alpha. Please see here: https://github.com/travis-ci/dpl/#maturity-levels
 
-### Nodejitsu:
+Options:
 
-#### Options:
+  Either api_key, or email and password are required.
 
-* **username**: Nodejitsu Username
-* **api-key**: Nodejitsu API Key
+  --api_key KEY        Engine Yard API key (type: string)
+  --email EMAIL        Engine Yard account email (type: string)
+  --password PASS      Engine Yard password (type: string)
+  --app APP            Engine Yard application name (type: string, default: repo name)
+  --env ENV            Engine Yard application environment (type: string, alias: environment)
+  --migrate CMD        Engine Yard migration commands (type: string)
+  --account NAME       Engine Yard account name (type: string)
 
-#### Examples:
-    dpl --provider=nodejitsu --username=<username> --api-key=<api-key>
+Common Options:
 
-### Engine Yard:
+  --run CMD            Command to execute after the deployment finished successfully (type: array
+                       (string, can be given multiple times))
+  --[no-]cleanup       Skip cleaning up build artifacts before the deployment
+  --help               Get help on this command
 
-#### Options:
+Examples:
 
-* **api-key**: Engine Yard Api Key
-* **username**: Engine Yard username. Not necessary if api-key is used. Requires git strategy.
-* **password**: Engine Yard password. Not necessary if api-key is used.
-* **app**: Engine Yard Application name. Defaults to git repo's name.
-* **environment**: Engine Yard Application Environment. Optional.
-* **migrate**: Engine Yard migration commands. Optional.
+  dpl engineyard --api_key key
+  dpl engineyard --email email --password pass
+  dpl engineyard --api_key key --app app --env env --migrate cmd --account name
+```
 
-#### Examples:
+### Firebase
 
-    dpl --provider=engineyard --api-key=<api-key>
-    dpl --provider=engineyard --username=<username> --password=<password> --environment=staging
-    dpl --provider=engineyard --api-key=<api-key> --app=<application> --migrate=`rake db:migrate`
+```
+Usage: dpl firebase [options]
 
-### OpenShift:
+Summary:
 
-#### Options:
+  Firebase deployment provider
 
-* **user**: Openshift Username.
-* **password**: Openshift Password.
-* **domain**: Openshift Application Domain.
-* **app**: Openshift Application. Defaults to git repo's name.
+Description:
 
-#### Examples:
+  tbd
 
-    dpl --provider=openshift --user=<username> --password=<password> --domain=<domain>
-    dpl --provider=openshift --user=<username> --password=<password> --domain=<domain> --app=<app>
+  Support for deployments to Firebase is in alpha. Please see here: https://github.com/travis-ci/dpl/#maturity-levels
 
-### RubyGems:
+Options:
 
-#### Options:
+  --token TOKEN        Firebase CI access token (generate with firebase login:ci) (type: string,
+                       required: true)
+  --project NAME       Firebase project to deploy to (defaults to the one specified in your
+                       firebase.json) (type: string)
+  --message MSG        Message describing this deployment. (type: string)
+  --only SERVICES      Firebase services to deploy (type: string, note: can be a comma-separated list)
+  --[no-]force         Whether or not to delete Cloud Functions missing from the current working
+                       directory
 
-* **api-key**: Rubygems Api Key.
-* **gemspec**: Optional. The name of the `gemspec` file to use to build the gem.
-* **gemspec_glob**: Optional. A glob pattern to search for gemspec files when multiple gems are generated in the repository.
-This _overrides_ the `gemspec` option.
+Common Options:
 
-#### Examples:
+  --run CMD            Command to execute after the deployment finished successfully (type: array
+                       (string, can be given multiple times))
+  --[no-]cleanup       Skip cleaning up build artifacts before the deployment
+  --help               Get help on this command
 
-    dpl --provider=rubygems --api-key=<api-key>
+Examples:
 
-### PyPI:
+  dpl firebase --token token
+  dpl firebase --token token --project name --message msg --only services --force
+```
 
-#### Options:
+### GitHub Pages
 
-* **user**: PyPI Username.
-* **password**: PyPI Password.
-* **server**: Optional. Only required if you want to release to a different index. Follows the form of 'https://mypackageindex.com/index'. Defaults to 'https://upload.pypi.org/legacy/'.
-* **distributions**: Optional. A space-separated list of distributions to be uploaded to PyPI. Defaults to 'sdist'.
-* **skip_upload_docs**: Optional. When set to `false`, documentation is uploaded. Defaults to `true`.
-  Note that upload.pypi.org does not support document uploading. If you set
-  this option to `false`, your deployment fails, unless you specify the server
-  that supports this option. See https://github.com/travis-ci/dpl/issues/660
-  for details.
-* **docs_dir**: Optional. A path to the directory to upload documentation from. Defaults to 'build/docs'
-* **skip_existing**: Optional. When set to `true`, the deployment will not fail if a file with the same name already exists on the server. It won't be uploaded and will not overwrite the existing file. Defaults to `false`.
+```
+Usage: dpl pages [options]
 
-#### Environment variables:
+Summary:
 
- * **PYPI_USER**: PyPI Username. Used if the `user` option is omitted.
- * **PYPI_PASSWORD**: PyPI Password. Used if the `password` option is omitted.
- * **PYPI_SERVER** Optional. Only required if you want to release to a different index. Used if the `server` option is omitted.
- * **PYPI_DISTRIBUTIONS** Optional. A space-separated list of distributions to be uploaded to PyPI. Used if the `distributions` option is omitted.
- * **PYPI_DOCS_DIR** Optional. A path to the directory to upload documentation from. Used if the `docs_dir` option is omitted.
+  GitHub Pages deployment provider
 
-#### Examples:
+Description:
 
-    dpl --provider=pypi --user=<username> --password=<password>
-    dpl --provider=pypi --user=<username> --password=<password> --server='https://mypackageindex.com/index' --distributions='sdist bdist_wheel'
+  tbd
 
-### npm:
+  Support for deployments to GitHub Pages is in alpha. Please see here: https://github.com/travis-ci/dpl/#maturity-levels
 
-#### Options:
+Options:
 
-* **email**: npm account email.
-* **api-key**: your [npm token](https://docs.npmjs.com/creating-and-viewing-authentication-tokens). _Can be retrieved from your ~/.npmrc file._
+  Either github_token, or deploy_key are required.
 
-#### Examples:
+  --github_token TOKEN           GitHub oauth token with repo permission (type: string)
+  --deploy_key KEY               A base64-encoded, private deploy key with write access to the repository (type:
+                                 string, note: RSA keys are too long to fit into a Travis CI secure variable, but
+                                 ECDSA-521 fits, see:
+                                 https://developer.github.com/v3/guides/managing-deploy-keys/#deploy-keys)
+  --repo SLUG                    Repo slug (type: string, default: repo slug)
+  --target_branch BRANCH         Branch to push force to (type: string, default: gh-pages)
+  --[no-]keep_history            Create incremental commit instead of doing push force (default: true)
+  --commit_message MSG           type: string, default: Deploy %{project_name} to %{url}:%{target_branch}
+  --[no-]allow_empty_commit      Allow an empty commit to be created (requires: keep_history)
+  --[no-]committer_from_gh       Use the token's owner name and email for commit. Overrides the email and name
+                                 options
+  --[no-]verbose                 Be verbose about the deploy process
+  --local_dir DIR                Directory to push to GitHub Pages (type: string, default: .)
+  --fqdn FQDN                    Writes your website's domain name to the CNAME file (type: string)
+  --project_name NAME            Used in the commit message only (defaults to fqdn or the current repo slug)
+                                 (type: string)
+  --email EMAIL                  Committer email (type: string, default: deploy@travis-ci.org)
+  --name NAME                    Committer name (type: string, default: Deploy Bot)
+  --[no-]deployment_file         Enable creation of a deployment-info file
+  --github_url URL               type: string, default: github.com
 
-    dpl --provider=npm --email=<email> --api-key=<token>
+Common Options:
 
-### S3:
+  --run CMD                      Command to execute after the deployment finished successfully (type: array
+                                 (string, can be given multiple times))
+  --[no-]cleanup                 Skip cleaning up build artifacts before the deployment
+  --help                         Get help on this command
 
-#### Options:
+Examples:
 
-* **access-key-id**: AWS Access Key ID. Can be obtained from [here](https://console.aws.amazon.com/iam/home?#security_credential).
-* **secret-access-key**: AWS Secret Key. Can be obtained from [here](https://console.aws.amazon.com/iam/home?#security_credential).
-* **bucket**: S3 Bucket.
-* **region**: S3 Region. Defaults to us-east-1.
-* **endpoint**: S3 Endpoint. Default is computed for you.
-* **upload-dir**: S3 directory to upload to. Defaults to root directory.
-* **storage-class**: S3 storage class to upload as. Defaults to "STANDARD". Other values are "STANDARD_IA" or "REDUCED_REDUNDANCY". Details can be found [here](https://aws.amazon.com/s3/storage-classes/).
-* **server-side-encryption**: When set to `true`, use S3 Server Side Encryption (SSE-AES256). Defaults to `false`.
-* **local-dir**: Local directory to upload from. Can be set from a global perspective (~/travis/build) or relative perspective (build) Defaults to project root.
-* **detect-encoding**: Set HTTP header `Content-Encoding` for files compressed with `gzip` and `compress` utilities. Defaults to not set.
-* **cache_control**: Set HTTP header `Cache-Control` to suggest that the browser cache the file. Defaults to `no-cache`. Valid options are `no-cache`, `no-store`, `max-age=<seconds>`,`s-maxage=<seconds>` `no-transform`, `public`, `private`.
-* **expires**: This sets the date and time that the cached object is no longer cacheable. Defaults to not set. The date must be in the format `YYYY-MM-DD HH:MM:SS -ZONE`.
-* **acl**: Sets the access control for the uploaded objects. Defaults to `private`. Valid options are `private`, `public_read`, `public_read_write`, `authenticated_read`, `bucket_owner_read`, `bucket_owner_full_control`.
-* **dot_match**: When set to `true`, upload files starting a `.`.
-* **index_document_suffix**: Set the index document of a S3 website.
-* **default_text_charset**: Set the default character set to append to the content-type of text files you are uploading.
-* **max_threads**: The number of threads to use for S3 file uploads. Default is 5, and the absolute maximum is 15.
+  dpl pages --github_token token
+  dpl pages --deploy_key key
+  dpl pages --github_token token --repo slug --target_branch branch --keep_history --commit_message msg
+```
 
-#### File-specific `Cache-Control` and `Expires` headers
+### GitHub Releases
 
-It is possible to set file-specific `Cache-Control` and `Expires` headers using `value: file[, file]` format.
+```
+Usage: dpl releases [options]
 
-#### Environment variables:
+Summary:
 
- * **AWS_ACCESS_KEY_ID**: AWS Access Key ID. Used if the `access-key-id` option is omitted.
- * **AWS_SECRET_ACCESS_KEY**: AWS Secret Key. Used if the `secret-access-key` option is omitted.
+  GitHub Releases deployment provider
 
-##### Example:
+Description:
 
-    --cache_control="no-cache: index.html"
-    --expires="\"2012-12-21 00:00:00 -0000\": *.css, *.js"
+  tbd
 
-#### Examples:
+  Support for deployments to GitHub Releases is in alpha. Please see here: https://github.com/travis-ci/dpl/#maturity-levels
 
-    dpl --provider=s3 --access-key-id=<access-key-id> --secret-access-key=<secret-access-key> --bucket=<bucket> --acl=public_read
-    dpl --provider=s3 --access-key-id=<access-key-id> --secret-access-key=<secret-access-key> --bucket=<bucket> --detect-encoding --cache_control=max-age=99999 --expires="2012-12-21 00:00:00 -0000"
-    dpl --provider=s3 --access-key-id=<access-key-id> --secret-access-key=<secret-access-key> --bucket=<bucket> --region=us-west-2 --local-dir=BUILD --upload-dir=BUILDS
+Options:
 
-### Using S3-compatible Object Storage
+  Either api_key, or user and password are required.
 
-By overriding the `endpoint` option, you can use an S3-compatible object storage such as [Digital Ocean Spaces](https://www.digitalocean.com/products/object-storage/).
+  --api_key TOKEN                GitHub oauth token (needs public_repo or repo permission) (type: string)
+  --username LOGIN               GitHub login name (type: string, alias: user)
+  --password PASS                GitHub password (type: string)
+  --repo SLUG                    GitHub repo slug (type: string, default: repo slug)
+  --file FILE                    File to release to GitHub (type: array (string, can be given multiple times),
+                                 required: true)
+  --[no-]file_glob               Interpret files as globs
+  --[no-]overwrite               Overwrite files with the same name
+  --[no-]prerelease              Identify the release as a prerelease
+  --release_number NUM           Release number (overide automatic release detection) (type: string)
+  --release_notes STR            Content for the release notes (type: string, alias: body)
+  --release_notes_file PATH      Path to a file containing the release notes (type: string, note: will be ignored
+                                 if --release_notes is given)
+  --[no-]draft                   Identify the release as a draft
+  --tag_name TAG                 Git tag from which to create the release (type: string)
+  --target_commitish STR         Commitish value that determines where the Git tag is created from (type: string)
+  --name NAME                    Name for the release (type: string)
 
-For example: `--endpoint=https://nyc3.digitaloceanspaces.com`
+Common Options:
 
-### Elastic Beanstalk:
+  --run CMD                      Command to execute after the deployment finished successfully (type: array
+                                 (string, can be given multiple times))
+  --[no-]cleanup                 Skip cleaning up build artifacts before the deployment
+  --help                         Get help on this command
 
-#### Options:
+Examples:
 
- * **access-key-id**: AWS Access Key ID. Can be obtained from [here](https://console.aws.amazon.com/iam/home?#security_credential).
- * **secret-access-key**: AWS Secret Key. Can be obtained from [here](https://console.aws.amazon.com/iam/home?#security_credential).
- * **region**: AWS Region the Elastic Beanstalk app is running in. Defaults to 'us-east-1'. Please be aware that this must match the region of the elastic beanstalk app.
- * **app**: Elastic Beanstalk application name.
- * **env**: Elastic Beanstalk environment name which will be updated.
- * **zip_file**: The zip file that you want to deploy. _**Note:**_ you also need to use the `skip_cleanup` or the zip file you are trying to upload will be removed during cleanup.
- * **bucket_name**: Bucket name to upload app to.
- * **bucket_path**: Location within Bucket to upload app to.
- * **only_create_app_version**: only create the app version, don't actually deploy it.
+  dpl releases --file file --api_key token
+  dpl releases --file file --password pass
+  dpl releases --file file
+  dpl releases --file file --api_key token --username login --repo slug --file_glob
+```
 
-#### Environment variables:
+### Google App Engine
 
- * **ELASTIC_BEANSTALK_ENV**: Elastic Beanstalk environment name which will be updated. Is only used if `env` option is omitted.
- * **ELASTIC_BEANSTALK_LABEL**: Label name of the new version.
- * **ELASTIC_BEANSTALK_DESCRIPTION**: Description of the new version. Defaults to the last commit message.
+```
+Usage: dpl gae [options]
 
-#### Examples:
+Summary:
 
-    dpl --provider=elasticbeanstalk --access-key-id=<access-key-id> --secret-access-key="<secret-access-key>" --app="example-app-name" --env="example-app-environment" --region="us-west-2"
+  Google App Engine deployment provider
 
-### OpsWorks:
+Description:
 
-#### Options:
+  tbd
 
-* **access-key-id**: AWS Access Key ID. Can be obtained from [here](https://console.aws.amazon.com/iam/home?#security_credential).
-* **secret-access-key**: AWS Secret Key. Can be obtained from [here](https://console.aws.amazon.com/iam/home?#security_credential).
-* **app-id**: The app ID.
-* **instance-ids**: An instance id. (Use this option multiple times to specify multiple instance ids. Default: [])
-* **layer-ids**: A layer id. (Use this option multiple times to specify multiple layer ids. Default: [])
-* **migrate**: Migrate the database. (Default: false)
-* **wait-until-deployed**: Wait until the app is deployed and return the deployment status. (Default: false)
-* **update-on-success**: When **wait-until-deployed** and **updated-on-success** are both `true`, application source is updated to the current SHA. Ignored when **wait-until-deployed** is false. (Default: false)
-* **custom_json**: Override custom_json options. If using this, default configuration will be overriden. See the code [here](https://github.com/travis-ci/dpl/blob/master/lib/dpl/provider/ops_works.rb#L43). More about `custom_json` [here](http://docs.aws.amazon.com/opsworks/latest/userguide/workingcookbook-json.html).
+  Support for deployments to Google App Engine is in alpha. Please see here: https://github.com/travis-ci/dpl/#maturity-levels
 
-#### Environment variables:
+Options:
 
- * **AWS_ACCESS_KEY_ID**: AWS Access Key ID. Used if the `access-key-id` option is omitted.
- * **AWS_SECRET_ACCESS_KEY**: AWS Secret Key. Used if the `secret-access-key` option is omitted.
+  --project ID                      Project ID used to identify the project on Google Cloud (type: string, required:
+                                    true)
+  --keyfile FILE                    Path to the JSON file containing your Service Account credentials in JSON Web
+                                    Token format. To be obtained via the Google Developers Console. Should be
+                                    handled with care as it contains authorization keys. (type: string, default:
+                                    service-account.json)
+  --config FILE                     Path to your service configuration file (type: array (string, can be given
+                                    multiple times), default: app.yaml)
+  --version VER                     The version of the app that will be created or replaced by this deployment. If
+                                    you do not specify a version, one will be generated for you (type: string)
+  --verbosity LEVEL                 Adjust the log verbosity (type: string, default: warning)
+  --[no-]promote                    Do not promote the deployed version (default: true)
+  --[no-]stop_previous_version      Prevent your deployment from stopping the previously promoted version. This is
+                                    from the future, so might not work (yet). (default: true)
+  --[no-]install_sdk                Do not install the Google Cloud SDK (default: true)
 
-#### Examples:
+Common Options:
 
-    dpl --provider=opsworks --access-key-id=<access-key-id> --secret-access-key=<secret-access-key> --app-id=<app-id> --migrate --wait-until-deployed
-    dpl --provider=opsworks --access-key-id=<access-key-id> --secret-access-key=<secret-access-key> --app-id=<app-id> --layer-ids=<layer-id>
+  --run CMD                         Command to execute after the deployment finished successfully (type: array
+                                    (string, can be given multiple times))
+  --[no-]cleanup                    Skip cleaning up build artifacts before the deployment
+  --help                            Get help on this command
 
-### Anynines:
+Examples:
 
-#### Options:
+  dpl gae --project id
+  dpl gae --project id --keyfile file --config file --version ver --verbosity level
+```
 
-* **username**: anynines username.
-* **password**: anynines password.
-* **organization**: anynines target organization.
-* **space**: anynines target space
-* **app_name**: Application name. Optional.
+### Google Cloud Store
 
-#### Examples:
+```
+Usage: dpl gcs [options]
 
-    dpl --provider=anynines --username=<username> --password=<password> --organization=<organization> --space=<space>
+Summary:
 
-### Atlas:
+  Google Cloud Store deployment provider
 
-The Atlas provider uses the [`atlas-upload-cli`](https://github.com/hashicorp/atlas-upload-cli) command. The [Atlas Upload CLI](https://github.com/hashicorp/atlas-upload-cli) is a lightweight command line interface for uploading application code to [Atlas](https://atlas.hashicorp.com/homepage?utm_source=github&utm_medium=travis-ci&utm_campaign=dpl) to kick off Atlas-based deployment processes from Travis CI.
+Description:
 
-You first need to create an [Atlas account](https://atlas.hashicorp.com/account/new?utm_source=github&utm_medium=travis-ci&utm_campaign=dpl), then, generate an [Atlas API token](https://atlas.hashicorp.com/settings/tokens) for Travis CI.
+  tbd
 
-#### Options:
+  Support for deployments to Google Cloud Store is in alpha. Please see here: https://github.com/travis-ci/dpl/#maturity-levels
 
-* **token** (Required): Atlas API token.
-* **app** (Required): Atlas application name (`<atlas-username>/<app-name>`).
-* **exclude**: Glob pattern of files or directories to exclude (this may be specified multiple times).
-* **include**: Glob pattern of files/directories to include (this may be specified multiple times, any excludes will override conflicting includes).
-* **address**: The address of the Atlas server.
-* **vcs**: Use VCS to determine which files to include/exclude.
-* **metadata**: Arbitrary key-value (string) metadata to be sent with the upload; may be specified multiple times.
-* **debug**: Turn on debug output.
-* **version**: Print the version of this application.
+Options:
 
-#### Examples:
+  --access_key_id ID           GCS Interoperable Access Key ID (type: string, required: true)
+  --secret_access_key KEY      GCS Interoperable Access Secret (type: string, required: true)
+  --bucket BUCKET              GCS Bucket (type: string, required: true)
+  --local_dir DIR              Local directory to upload from (type: string, default: .)
+  --upload_dir DIR             GCS directory to upload to (type: string)
+  --[no-]dot_match             Upload hidden files starting with a dot
+  --acl ACL                    Access control to set for uploaded objects (type: string)
+  --[no-]detect_encoding       HTTP header Content-Encoding to set for files compressed with gzip and compress
+                               utilities.
+  --cache_control HEADER       HTTP header Cache-Control to suggest that the browser cache the file. (type:
+                               string)
 
-    dpl --provider=atlas --token=ATLAS_TOKEN --app=ATLAS_USERNAME/APP_NAME
-    dpl --provider=atlas --token=ATLAS_TOKEN --app=ATLAS_USERNAME/APP_NAME --debug --vcs --version
-    dpl --provider=atlas --token=ATLAS_TOKEN --app=ATLAS_USERNAME/APP_NAME --exclude="*.log" --include="build/*" --include="bin/*"
-    dpl --provider=atlas --token=ATLAS_TOKEN --app=ATLAS_USERNAME/APP_NAME --metadata="foo=bar" --metadata="bar=baz"
+Common Options:
 
-### Azure Web Apps:
+  --run CMD                    Command to execute after the deployment finished successfully (type: array
+                               (string, can be given multiple times))
+  --[no-]cleanup               Skip cleaning up build artifacts before the deployment
+  --help                       Get help on this command
 
-#### Options:
+Examples:
 
-* **site**: Web App Name (if your app lives at myapp.azurewebsites.net, the name would be myapp).
-* **slot**: Optional. Slot name if your app uses staging deployment. (e.g. if your slot lives at myapp-test.azurewebsites.net, the slot would be myapp-test).
-* **username**: Web App Deployment Username.
-* **password**: Web App Deployment Password.
-* **verbose**: If passed, Azure's deployment output will be printed. Warning: If you provide incorrect credentials, Git will print those in clear text. Correct authentication credentials will remain hidden.
+  dpl gcs --access_key_id id --secret_access_key key --bucket bucket
+  dpl gcs --access_key_id id --secret_access_key key --bucket bucket --local_dir dir --upload_dir dir
+```
 
-#### Environment variables:
+### Hackage
 
- * **AZURE_WA_SITE** Web App Name. Used if the `site` option is omitted.
- * **AZURE_WA_SLOT** Optional. Slot name if your app uses staging deployment. Used if the `slot` option is omitted.
- * **AZURE_WA_USERNAME**: Web App Deployment Username. Used if the `username` option is omitted.
- * **AZURE_WA_PASSWORD**: Web App Deployment Password. Used if the `password` option is omitted.
+```
+Usage: dpl hackage [options]
 
-#### Examples:
+Summary:
 
-    dpl --provider=AzureWebApps --username=depluser --password=deplp@ss --site=dplsite --slot=dplsite-test --verbose
+  Hackage deployment provider
 
-### Cloud Foundry:
+Description:
 
-#### Options:
+  tbd
 
-* **username**: Cloud Foundry username.
-* **password**: Cloud Foundry password.
-* **organization**: Cloud Foundry target organization.
-* **api**: Cloud Foundry api URL
-* **space**: Cloud Foundry target space
-* **app_name**: Application name. Optional.
-* **manifest**: Path to manifest file. Optional.
-* **skip_ssl_validation**: Skip ssl validation. Optional.
+  Support for deployments to Hackage is in alpha. Please see here: https://github.com/travis-ci/dpl/#maturity-levels
 
-#### Examples:
+Options:
 
-    dpl --provider=cloudfoundry --username=<username> --password=<password> --organization=<organization> --api=<api> --space=<space> --skip-ssl-validation
+  --username USER      Hackage username (type: string, required: true)
+  --password USER      Hackage password (type: string, required: true)
+  --[no-]publish       Whether or not to publish the package
 
-### cargo:
+Common Options:
 
-#### Options:
+  --run CMD            Command to execute after the deployment finished successfully (type: array
+                       (string, can be given multiple times))
+  --[no-]cleanup       Skip cleaning up build artifacts before the deployment
+  --help               Get help on this command
 
-* **token**: Your cargo registry API token, for crates.io generate at <https://crates.io/me>
+Examples:
 
-#### Examples:
+  dpl hackage --username user --password user
+  dpl hackage --username user --password user --publish --run cmd --cleanup
+```
 
-    dpl --provider=cargo --token=<token>
+### Hephy
 
-### Rackspace Cloud Files:
+```
+Usage: dpl hephy [options]
 
-#### Options:
+Summary:
 
-* **username**: Rackspace Username.
-* **api-key**: Rackspace API Key.
-* **region**: Cloud Files Region. The region in which your Cloud Files container exists.
-* **container**: Container Name. The container where you would like your files to be uploaded.
-* **dot_match**: When set to `true`, upload files starting a `.`.
+  Hephy deployment provider
 
-#### Examples:
+Description:
 
-    dpl --provider=cloudfiles --username=<username> --api-key=<api-key> --region=<region> --container=<container>
+  tbd
 
-### GitHub Pages:
+  Support for deployments to Hephy is in alpha. Please see here: https://github.com/travis-ci/dpl/#maturity-levels
 
-#### Options:
+Options:
 
-* **github-token**: GitHub oauth token with `repo` permission.
-* **repo**: Repo slug, defaults to current one.
-* **target-branch**: Branch to push force to, defaults to gh-pages.
-* **keep-history**: Optional, create incremental commit instead of doing push force, defaults to false.
-* **allow-empty-commit**: Optional, defaults to false. Enabled if only keep-history is true.
-* **committer-from-gh**: Optional, defaults to false. Allows to use token's owner name and email for commit. Overrides `email` and `name` options.
-* **verbose**: Optional, be verbose about internal steps, defaults to false.
-* **local-dir**: Directory to push to GitHub Pages, defaults to current.
-* **fqdn**: Optional, no default, sets a main domain for your website.
-* **project-name**: Defaults to fqdn or repo slug, used for metadata.
-* **email**: Optional, committer info, defaults to deploy@travis-ci.org.
-* **name**: Optional, committer, defaults to Deployment Bot.
-* **deployment-file**: Optional, defaults to false, enables creation of deployment-info files
+  --controller NAME      Hephy controller (type: string, required: true, e.g.: hephy.hephyapps.com)
+  --username USER        Hephy username (type: string, required: true)
+  --password PASS        Hephy password (type: string, required: true)
+  --app APP              Deis app (type: string, required: true)
+  --cli_version VER      Install a specific hephy cli version (type: string, default: stable)
+  --[no-]verbose         Verbose log output
 
-#### Examples:
+Common Options:
 
-    dpl --provider=pages --github-token=<api-key> --local-dir=build
+  --run CMD              Command to execute after the deployment finished successfully (type: array
+                         (string, can be given multiple times))
+  --[no-]cleanup         Skip cleaning up build artifacts before the deployment
+  --help                 Get help on this command
 
-### GitHub Releases:
+Examples:
 
-#### Options:
+  dpl hephy --controller name --username user --password pass --app app
+  dpl hephy --controller name --username user --password pass --app app --cli_version ver
+```
 
-* **api-key**: GitHub oauth token with `public_repo` or`repo` permission.
-* **user**: GitHub username. Not necessary if `api-key` is used.
-* **password**: GitHub Password. Not necessary if `api-key` is used.
-* **repo**: GitHub Repo. Defaults to git repo's name.
-* **file**: File to upload to GitHub Release.
-* **file_glob**: If files should be interpreted as globs (\* and \*\* wildcards). Defaults to false.
-* **overwrite**: If files with the same name should be overwritten. Defaults to false.
-* **release-number**: Overide automatic release detection, set a release manually.
-* **prerelease**: Identify the release as a prerelease.
+### Heroku API
 
-Additionally, options can be passed to [Octokit](https://github.com/octokit/octokit.rb) client.
-These are documented in https://github.com/octokit/octokit.rb/blob/master/lib/octokit/client/releases.rb.
+```
+Usage: dpl heroku api [options]
 
-#### GitHub Two Factor Authentication
+Summary:
 
-For accounts using two factor authentication, you have to use an oauth token as a username and password will not work.
+  Heroku API deployment provider
 
-#### Examples:
+Description:
 
-    dpl --provider=releases --api-key=<api-key> --file=build.tar.gz
+  tbd
 
-### Cloud 66
+  Support for deployments to Heroku API is in alpha. Please see here: https://github.com/travis-ci/dpl/#maturity-levels
 
-#### Options:
+Options:
 
-* **redeployment_hook**: The redeployment hook URL. Available from the Information menu within the Cloud 66 portal.
+  --api_key KEY       Heroku API key (type: string, required: true)
 
-#### Examples:
+Common Options:
 
-    dpl --provider=cloud66 --redeployment_hook=<url>
+  --run CMD           Command to execute after the deployment finished successfully (type: array
+                      (string, can be given multiple times))
+  --[no-]cleanup      Skip cleaning up build artifacts before the deployment
+  --app APP           Heroku app name (type: string, default: repo name)
+  --help              Get help on this command
 
-### Hackage:
+Examples:
 
-#### Options:
+  dpl heroku api --api_key key
+  dpl heroku api --api_key key --run cmd --cleanup --app app
+```
 
-* **username**: Hackage username.
-* **password**: Hackage password.
+### Heroku Git
 
-#### Examples:
+```
+Usage: dpl heroku git [options]
 
-    dpl --provider=hackage --username=<username> --password=<password>
+Summary:
 
-### Deis:
+  Heroku Git deployment provider
 
-#### Options:
+Description:
 
-* **controller**: Deis controller e.g. deis.deisapps.com
-* **username**: Deis username
-* **password**: Deis password
-* **app**: Deis app
-* **cli_version**: Install a specific deis cli version
+  tbd
 
-#### Examples:
+  Support for deployments to Heroku Git is in alpha. Please see here: https://github.com/travis-ci/dpl/#maturity-levels
 
-    dpl --provider=deis --controller=deis.deisapps.com --username=travis --password=secret --app=example
+Options:
 
-### Hephy:
+  Either api_key, or username and password are required.
 
-#### Options:
+  --api_key KEY        Heroku API key (type: string)
+  --username USER      Heroku username (type: string, alias: user)
+  --password PASS      Heroku password (type: string)
+  --git URL            type: string
 
-* **controller**: Hephy controller e.g. hephy.hephyapps.com
-* **username**: Hephy username
-* **password**: Hephy password
-* **app**: Hephy app
-* **cli_version**: Install a specific hephy cli version
+Common Options:
 
-#### Examples:
+  --run CMD            Command to execute after the deployment finished successfully (type: array
+                       (string, can be given multiple times))
+  --[no-]cleanup       Skip cleaning up build artifacts before the deployment
+  --app APP            Heroku app name (type: string, default: repo name)
+  --help               Get help on this command
 
-    dpl --provider=hephy --controller=hephy.hephyapps.com --username=travis --password=secret --app=example
+Examples:
 
-### Google Cloud Storage:
+  dpl heroku git --api_key key
+  dpl heroku git --username user --password pass
+  dpl heroku git --api_key key --git url --run cmd --cleanup --app app
+```
 
-#### Options:
+### Launchpad
 
-* **access-key-id**: GCS Interoperable Access Key ID. Info about Interoperable Access Key from [here](https://developers.google.com/storage/docs/migrating).
-* **secret-access-key**: GCS Interoperable Access Secret.
-* **bucket**: GCS Bucket.
-* **upload-dir**: GCS directory to upload to. Defaults to root directory.
-* **local-dir**: Local directory to upload from. Can be set from a global perspective (~/travis/build) or relative perspective (build) Defaults to project root.
-* **dot_match**: When set to `true`, upload files starting a `.`.
-* **detect-encoding**: Set HTTP header `Content-Encoding` for files compressed with `gzip` and `compress` utilities. Defaults to not set.
-* **cache_control**: Set HTTP header `Cache-Control` to suggest that the browser cache the file. Defaults to not set. Info is [here](https://developers.google.com/storage/docs/reference-headers#cachecontrol)
-* **acl**: Sets the access control for the uploaded objects. Defaults to not set. Info is [here](https://developers.google.com/storage/docs/reference-headers#xgoogacl)
+```
+Usage: dpl launchpad [options]
 
-#### Examples:
+Summary:
 
-    dpl --provider=gcs --access-key-id=<access-key-id> --secret-access-key=<secret-access-key> --bucket=<bucket>
-    dpl --provider=gcs --access-key-id=<access-key-id> --secret-access-key=<secret-access-key> --bucket=<bucket> --local-dir= BUILD
-    dpl --provider=gcs --access-key-id=<access-key-id> --secret-access-key=<secret-access-key> --bucket=<bucket> --acl=public-read
-    dpl --provider=gcs --access-key-id=<access-key-id> --secret-access-key=<secret-access-key> --bucket=<bucket> --detect-encoding --cache_control=max-age=99999
-    dpl --provider=gcs --access-key-id=<access-key-id> --secret-access-key=<secret-access-key> --bucket=<bucket> --local-dir=BUILD --upload-dir=BUILDS
+  Launchpad deployment provider
 
-### BitBalloon:
+Description:
 
-#### Options:
+  tbd
 
- * **access_token**: Optional. The access_token which can be found in the `.bitballoon` file after a deployment using the bitballoon CLI. Only required if no `.bitballoon` file is present.
- * **site_id**: Optional. The site_id which can be found in the .bitballoon file after a deployment using the bitballoon CLI. Only required if no `.bitballoon` file is present.
- * **local_dir**: Optional. The sub-directory of the built assets for deployment. Default to current path.
+  Support for deployments to Launchpad is in alpha. Please see here: https://github.com/travis-ci/dpl/#maturity-levels
 
-#### Examples:
+Options:
 
-    dpl --access-token=<access-token> --site-id=3f932c1e-708b-4573-938a-a07d9728c22e
-    dpl --access-token=<access-token> --site-id=3f932c1e-708b-4573-938a-a07d9728c22e --local-dir=build
+  --slug SLUG                      Launchpad project slug (type: string, format: /^~[^\/]+\/[^\/]+\/[^\/]+$/, e.g.:
+                                   ~user-name/project-name/branch-name)
+  --oauth_token TOKEN              Launchpad OAuth token (type: string)
+  --oauth_token_secret SECRET      Launchpad OAuth token secret (type: string)
 
-### Puppet Forge:
+Common Options:
 
-#### Options:
+  --run CMD                        Command to execute after the deployment finished successfully (type: array
+                                   (string, can be given multiple times))
+  --[no-]cleanup                   Skip cleaning up build artifacts before the deployment
+  --help                           Get help on this command
 
- * **user**: Required. The user name at Puppet forge.
- * **password**: Required. The Puppet forge password.
- * **url**: Optional. The forge URL to deploy to. Defaults to https://forgeapi.puppetlabs.com/
+Examples:
 
-#### Examples:
+  dpl launchpad --slug slug --oauth_token token --oauth_token_secret secret --run cmd --cleanup
+```
 
-    dpl --provider=puppetforge --user=puppetlabs --password=s3cr3t
+### Netlify
 
-### packagecloud:
+```
+Usage: dpl netlify [options]
 
-#### Options:
+Summary:
 
- * **username**: Required. The packagecloud.io username.
- * **token**: Required. The [packagecloud.io api token](https://packagecloud.io/docs/api#api_tokens).
- * **repository**: Required. The repository to push to.
- * **local_dir**: Optional. The sub-directory of the built assets for deployment. Default to current path.
- * **dist**: Required for debian, rpm, and node.js packages. The complete list of supported strings can be found on the [packagecloud.io docs](https://packagecloud.io/docs#os_distro_version). For node.js packages, simply use "node".
- * **force**: Optional. Whether package has to be (re)uploaded / deleted before upload
+  Netlify deployment provider
 
-#### Examples:
+Description:
 
-    dpl --provider=packagecloud --username=packageuser --token=t0k3n --repository=myrepo
-    dpl --provider=packagecloud --username=packageuser --token=t0k3n --repository=myrepo --dist=ubuntu/precise
-    dpl --provider=packagecloud --username=packageuser --token=t0k3n --repository=myrepo --local-dir="${TRAVIS_BUILD_DIR}/pkgs" --dist=ubuntu/precise
+  tbd
 
-### Catalyze:
+  Support for deployments to Netlify is in alpha. Please see here: https://github.com/travis-ci/dpl/#maturity-levels
 
-#### Options:
+Options:
 
- * **target**: Required. The git remote repository to deploy to.
- * **path**: Optional. If using the skip_cleanup option to deploy from current file state, you can optionally specify the pathspec for the files to deploy. If not specified then all files are deployed.
+  --site ID              A site ID to deploy to (type: string, required: true)
+  --auth TOKEN           An auth token to log in with (type: string, required: true)
+  --dir DIR              Specify a folder to deploy (type: string)
+  --functions FUNCS      Specify a functions folder to deploy (type: string)
+  --message MSG          A message to include in the deploy log (type: string)
+  --[no-]prod            Deploy to production
 
-#### Examples:
+Common Options:
 
-    dpl --provider=catalyze --target=ssh://git@git.catalyzeapps.com:2222/app1234.git
-    dpl --provider=catalyze --target=ssh://git@git.catalyzeapps.com:2222/app1234.git --skip_cleanup=true
-    dpl --provider=catalyze --target=ssh://git@git.catalyzeapps.com:2222/app1234.git --skip_cleanup=true --path=build
+  --run CMD              Command to execute after the deployment finished successfully (type: array
+                         (string, can be given multiple times))
+  --[no-]cleanup         Skip cleaning up build artifacts before the deployment
+  --help                 Get help on this command
 
+Examples:
 
-#### Setup:
+  dpl netlify --site id --auth token
+  dpl netlify --site id --auth token --dir dir --functions funcs --message msg
+```
 
-1. Get the deployment target for Catalyze:
-  1. Make sure your catalyze environment is [associated](https://resources.catalyze.io/paas/paas-cli-reference/#associate).
-  2. Get the git remote by running ```git remote -v``` from within the associated repo.
-2. Setup a deployment key to Catalyze for Travis CI:
-  1. Install the travis-ci cli.
-  2. Get the public SSH key for your travis project and save it to a file by running ```travis pubkey > travis.pub```
-  3. Add the key as a deploy key using the catalyze cli within the associated repo. For example:  ```catalyze deploy-keys add travisci ./travis.pub code-1```
-3. Setup Catalyze as a known host for Travis CI:
-  1. List your known hosts by running ```cat ~/.ssh/known_hosts```
-  2. Find and copy the line from known_hosts that includes the git remote found in step #1. It'll look something like "[git.catalyzeapps.com]:2222 ecdsa-sha2-nistp256 BBBB12abZmKlLXNo..."
-  3. Update your `before_deploy` step in `.travis.yml` to update the `known_hosts` file:
+### npm
 
-  ```
-  before_deploy:  echo "[git.catalyzeapps.com]:2222 ecdsa-sha2-nistp256 BBBB12abZmKlLXNo..." >> ~/.ssh/known_hosts
-  ```
+```
+Usage: dpl npm [options]
 
-### Chef Supermarket:
+Summary:
 
-#### Options:
+  npm deployment provider
 
- * **user_id**: Required. The user name at Chef Supermarket.
- * **client_key**: Required. The client API key file name.
- * **cookbook_category**: Required. The cookbook category in Supermarket (see: https://docs.getchef.com/knife_cookbook_site.html#id12 )
+Description:
 
-#### Examples:
+  tbd
 
-    dpl --provider=chef-supermarket --user-id=chef --client-key=.travis/client.pem --cookbook-category=Others
+  Support for deployments to npm is in alpha. Please see here: https://github.com/travis-ci/dpl/#maturity-levels
 
-### Lambda:
+Options:
 
-#### Options:
+  --email EMAIL           npm account email (type: string)
+  --api_token TOKEN       npm api token (type: string, required: true, alias: api_key, note: can be
+                          retrieved from your local ~/.npmrc file, see:
+                          https://docs.npmjs.com/creating-and-viewing-authentication-tokens)
+  --access ACCESS         Access level (type: string, known values: public, private)
+  --registry URL          npm registry url (type: string)
+  --src SRC               directory or tarball to publish (type: string, default: .)
+  --tag TAGS              distribution tags to add (type: string)
+  --[no-]auth_method      Authentication method (known values: auth)
 
- * **access_key_id**: AWS Access Key ID. Can be obtained from [here](https://console.aws.amazon.com/iam/home?#security_credential).
- * **secret_access_key**: AWS Secret Key. Can be obtained from [here](https://console.aws.amazon.com/iam/home?#security_credential).
- * **region**: AWS Region the Lambda function is running in. Defaults to 'us-east-1'.
- * **function_name**: Required. The name of the Lambda being created / updated.
- * **role**: Required. The ARN of the IAM role to assign to this Lambda function.
- * **handler_name**: Required. The function that Lambda calls to begin execution. For NodeJS, it is exported function for the module.
- * **dot_match**: Optional. When `true`, the zipped archive will include the hidden `.*` files. Defaults to `false`.
- * **module_name**: Optional. The name of the module that exports the handler. Defaults to `index`.
- * **zip**: Optional. Either a path to an existing packaged (zipped or jar file) Lambda, a directory to package, or a single file to package. Defaults to `Dir.pwd`.
- * **description**: Optional. The description of the Lambda being created / updated. Defaults to "Deploy build #{context.env['TRAVIS_BUILD_NUMBER']} to AWS Lambda via Travis CI"
- * **timeout**: Optional. The function execution time at which Lambda should terminate the function. Defaults to 3 (seconds).
- * **memory_size**: Optional. The amount of memory in MB to allocate to this Lambda. Defaults to 128.
- * **runtime**: Optional. The Lambda runtime to use. Defaults to `node`.
- * **publish**: If `true`, a [new version](http://docs.aws.amazon.com/lambda/latest/dg/versioning-intro.html#versioning-intro-publish-version) of the Lambda function will be created instead of replacing the code of the existing one.
- * **subnet_ids**: Optional. List of subnet IDs to be added to the function. Needs the `ec2:DescribeSubnets` and `ec2:DescribeVpcs` permission for the user of the access/secret key to work.
- * **security_group_ids**: Optional. List of security group IDs to be added to the function. Needs the `ec2:DescribeSecurityGroups` and `ec2:DescribeVpcs` permission for the user of the access/secret key to work.
- * **dead_letter_arn**: Optional. ARN to an SNS or SQS resource used for the dead letter queue. [More about DLQs here](https://docs.aws.amazon.com/lambda/latest/dg/dlq.html).
- * **tracing_mode**: Optional. "Active" or "PassThrough" only. Default is "PassThrough".  Needs the `xray:PutTraceSegments` and `xray:PutTelemetryRecords` on the role for this to work. [More on
- Active Tracing here](https://docs.aws.amazon.com/lambda/latest/dg/lambda-x-ray.html).
- * **environment_variables**: Optional. List of Environment Variables to add to the function, needs to be in the format of `KEY=VALUE`. Can be encrypted for added security.
- * **kms_key_arn**: Optional. KMS key ARN to use to encrypt `environment_variables`.
- * **function_tags**: Optional. List of tags to add to the function, needs to be in the format of `KEY=VALUE`. Can be encrypted for added security.
+Common Options:
 
- For a list of all [permissions for Lambda, please refer to the documentation](https://docs.aws.amazon.com/lambda/latest/dg/lambda-api-permissions-ref.html).
+  --run CMD               Command to execute after the deployment finished successfully (type: array
+                          (string, can be given multiple times))
+  --[no-]cleanup          Skip cleaning up build artifacts before the deployment
+  --help                  Get help on this command
 
-#### Examples:
+Examples:
 
-Deploy contents of current working directory using default module:
+  dpl npm --api_token token
+  dpl npm --api_token token --email email --access public --registry url --src src
 ```
-    dpl --provider="lambda" \
-        --access_key_id="${AWS_ACCESS_KEY}" \
-        --secret_access_key="${AWS_SECRET_KEY}" \
-        --function_name="test-lambda" \
-        --role="${AWS_LAMBDA_ROLE}" \
-        --handler_name="handler";
+
+### OpenShift
+
 ```
-Deploy contents of a specific directory using specific module name:
+Usage: dpl openshift [options]
+
+Summary:
+
+  OpenShift deployment provider
+
+Description:
+
+  tbd
+
+  Support for deployments to OpenShift is in alpha. Please see here: https://github.com/travis-ci/dpl/#maturity-levels
+
+Options:
+
+  --server SERVER        OpenShift server (type: string, required: true)
+  --token TOKEN          OpenShift token (type: string, required: true)
+  --project PROJECT      OpenShift project (type: string, required: true)
+  --app APP              OpenShift application (type: string, default: repo name)
+
+Common Options:
+
+  --run CMD              Command to execute after the deployment finished successfully (type: array
+                         (string, can be given multiple times))
+  --[no-]cleanup         Skip cleaning up build artifacts before the deployment
+  --help                 Get help on this command
+
+Examples:
+
+  dpl openshift --server server --token token --project project
+  dpl openshift --server server --token token --project project --app app --run cmd
 ```
-    dpl --provider="lambda" \
-        --access_key_id="${AWS_ACCESS_KEY}" \
-        --secret_access_key="${AWS_SECRET_KEY}" \
-        --function_name="test-lambda" \
-        --role="${AWS_LAMBDA_ROLE}" \
-        --zip="${TRAVIS_BUILD_DIR}/dist"  \
-        --module_name="copy" \
-        --handler_name="handler";
+
+### Packagecloud
+
 ```
+Usage: dpl packagecloud [options]
+
+Summary:
+
+  Packagecloud deployment provider
+
+Description:
+
+  tbd
+
+  Support for deployments to Packagecloud is in alpha. Please see here: https://github.com/travis-ci/dpl/#maturity-levels
 
-### Launchpad:
+Options:
 
-#### Options:
+  --username USER            The packagecloud.io username. (type: string, required: true)
+  --token TOKEN              The packagecloud.io api token. (type: string, required: true)
+  --repository REPO          The repository to push to. (type: string, required: true)
+  --local_dir DIR            The sub-directory of the built assets for deployment. (type: string, default: .)
+  --dist DIST                Required for debian, rpm, and node.js packages (use "node" for node.js
+                             packages). The complete list of supported strings can be found on the
+                             packagecloud.io docs. (type: string)
+  --[no-]force               Whether package has to be (re)uploaded / deleted before upload
+  --connect_timeout SEC      type: integer, default: 60
+  --read_timeout SEC         type: integer, default: 60
+  --write_timeout SEC        type: integer, default: 180
+  --package_glob GLOB        type: array (string, can be given multiple times), default: ["**/*"]
 
- * **slug**: Required. `~user-name/project-name/branch-name`
- * **oauth_token**: Required. Your OAUTH token for Launchpad
- * **oauth_token_secret**: Required. Your OAUTH token secret for Launchpad
+Common Options:
 
-#### Example:
+  --run CMD                  Command to execute after the deployment finished successfully (type: array
+                             (string, can be given multiple times))
+  --[no-]cleanup             Skip cleaning up build artifacts before the deployment
+  --help                     Get help on this command
 
-Deploy contents of current working directory using default module:
+Examples:
+
+  dpl packagecloud --username user --token token --repository repo
+  dpl packagecloud --username user --token token --repository repo --local_dir dir --dist dist
 ```
-    dpl --provider="launchpad" \
-        --slug="~user-name/project-name/branch-name" \
-        --oauth_token="${LAUNCHPAD_OAUTH_TOKEN}" \
-        --oauth_token_secret="${LAUNCHPAD_OAUTH_TOKEN_SECRET}";
+
+### Puppet Forge
+
 ```
+Usage: dpl puppetforge [options]
+
+Summary:
+
+  Puppet Forge deployment provider
+
+Description:
+
+  tbd
+
+  Support for deployments to Puppet Forge is in alpha. Please see here: https://github.com/travis-ci/dpl/#maturity-levels
 
-### TestFairy:
+Options:
 
-Your Android(apk)/iOS(ipa) file will be uploaded to TestFairy,
-and your testers can start testing your app.
+  --username NAME      Puppet Forge user name (type: string, required: true, alias: user)
+  --password PASS      Puppet Forge password (type: string, required: true)
+  --url URL            Puppet Forge URL to deploy to (type: string, default:
+                       https://forgeapi.puppetlabs.com/)
 
-#### Options:
-* **api-key**: TestFairy API Key (https://app.testfairy.com/settings/) run "travis encrypt --add deploy.api-key" on your repo.
-* **app-file**: Path to the app file that will be generated after the build (APK/IPA).
-* **symbols-file**: Path to the symbols file.
-* **testers-groups**: You can set a tester group to be notified about this build (group1,group1).
-* **notify**: If true, an email you a changelog will be sent to your users.
-* **auto-update**: If true, all the previous installations of this app will be automatically all upgraded to this version.
-* **video-quality**: Video quality settings, "high", "medium" or "low". Default is "high".
-* **screenshot-interval**: You can choose "1"\"2"\"10" sec.
-* **max-duration**: Maximum session recording length, eg "20m" or "1h". Default is "10m". Maximum "24h".
-* **advanced-options**: For example (option1,option2)
-* **data-only-wifi**: If true, video and recorded metrics will be sent only when connected to a wifi network.
-* **record-on-background**: If true, data will be collected while the app on background.
-* **video**: If true, Video recording settings "true", "false". Default is "true".
-* **icon-watermark**: Add a small watermark to app icon. Default is "false".
-* **metrics**: Comma-separated list of metrics to record. View list on http://docs.testfairy.com/Upload_API.html.
+Common Options:
 
-#### Examples:
+  --run CMD            Command to execute after the deployment finished successfully (type: array
+                       (string, can be given multiple times))
+  --[no-]cleanup       Skip cleaning up build artifacts before the deployment
+  --help               Get help on this command
 
-    dpl --provider=testfairy --api-key=<api-key> --app-file="out/Sample.apk" --keystore-file="out/keystore" --storepass=<storepass> --alias=<alias>
+Examples:
 
-### AWS CodeDeploy:
+  dpl puppetforge --username name --password pass
+  dpl puppetforge --username name --password pass --url url --run cmd --cleanup
+```
+
+### PyPI
+
+```
+Usage: dpl pypi [options]
 
-#### Options:
+Summary:
 
-* **access_key_id**: AWS Access Key.
-* **secret_access_key**: AWS Secret Access Key.
-* **application**: CodeDeploy Application Name.
-* **deployment_group**: CodeDeploy Deployment Group Name.
-* **revision_type**: CodeDeploy Revision Type (S3 or GitHub).
-* **commit_id**: Commit ID in case of GitHub.
-* **repository**: Repository Name in case of GitHub.
-* **bucket**: S3 bucket in case of S3.
-* **region**: AWS Availability Zone.
-* **wait_until_deployed**: Wait until the app is deployed and return the deployment status (Optional, Default false).
+  PyPI deployment provider
 
-#### Environment variables:
+Description:
 
- * **AWS_ACCESS_KEY_ID**: AWS Access Key ID. Used if the `access_key_id` option is omitted.
- * **AWS_SECRET_ACCESS_KEY**: AWS Secret Key. Used if the `secret_access_key` option is omitted.
+  tbd
 
-#### Examples:
+  Support for deployments to PyPI is in alpha. Please see here: https://github.com/travis-ci/dpl/#maturity-levels
 
-    dpl --provider=codedeploy --access_key_id=<aws access key> --secret_access_key=<aws secret access key> --application=<application name> --deployment_group=<deployment group> --revision_type=<s3/github> --bucket=<bucket name> --commit_id=<commit ID> --repository=<repo name> --region=<AWS availability zone> --wait_until_deployed=<true>
+Options:
 
-### Scalingo:
+  --username NAME               PyPI Username (type: string, required: true, alias: user)
+  --password PASS               PyPI Password (type: string, required: true)
+  --server SERVER               Release to a different index (type: string, default:
+                                https://upload.pypi.org/legacy/)
+  --distributions DISTS         Space-separated list of distributions to be uploaded to PyPI (type: string,
+                                default: sdist)
+  --docs_dir DIR                Path to the directory to upload documentation from (type: string, default:
+                                build/docs)
+  --[no-]skip_existing          Do not overwrite an existing file with the same name on the server.
+  --[no-]upload_docs            Upload documentation (default: false, note: most PyPI servers, including
+                                upload.pypi.org, do not support uploading documentation)
+  --[no-]twine_check            Whether to run twine check (default: true)
+  --[no-]remove_build_dir       Remove the build dir after the upload (default: true)
+  --setuptools_version VER      type: string, format: /\A\d+(?:\.\d+)*\z/
+  --twine_version VER           type: string, format: /\A\d+(?:\.\d+)*\z/
+  --wheel_version VER           type: string, format: /\A\d+(?:\.\d+)*\z/
 
-#### Options:
-* **api_key**: scalingo API Key. Not necessary if username and password are used.
-* **username**: scalingo username. Not necessary if api_key is used.
-* **password**: scalingo password. Not necessary if api_key is used.
-* **remote**: Remote url or git remote name of your git repository. By default remote name is "scalingo".
-* **branch**: Branch of your git repository. By default branch name is "master".
-* **app**: Only necessary if your repository does not contain the appropriate remote. Specifying the app will add a remote to your local repository: `git remote add <remote> git@scalingo.com:<app>.git`
+Common Options:
 
-#### Use:
+  --run CMD                     Command to execute after the deployment finished successfully (type: array
+                                (string, can be given multiple times))
+  --[no-]cleanup                Skip cleaning up build artifacts before the deployment
+  --help                        Get help on this command
 
-You can connect to Scalingo using your username/password or your api key.
-It needs [Scalingo CLI](http://cli.scalingo.com/) which will be [downloaded here](http://cli.scalingo.com/).
-Then, it will push your project to Scalingo and deploy it automatically.
+Examples:
 
-Note: You only need to connect once to Scalingo CLI, credentials are stored locally.
+  dpl pypi --username name --password pass
+  dpl pypi --username name --password pass --server server --distributions dists --docs_dir dir
+```
 
-#### Examples:
+### Rubygems
 
-    dpl --provider=scalingo --api_key="aaAAbbBB0011223344"
-    dpl --provider=scalingo --username=<username> --password=<password>
+```
+Usage: dpl rubygems [options]
 
-    dpl --provider=scalingo --api_key="aaAAbbBB0011223344" --remote="scalingo-staging"
-    dpl --provider=scalingo --api_key="aaAAbbBB0011223344" --remote="scalingo-staging" --branch="master"
+Summary:
 
-    dpl --provider=scalingo
+  Rubygems deployment provider
 
-### Script:
+Description:
 
-An elementary provider that executes a single command.
+  tbd
 
-Deployment will be marked a failure if the script exits with nonzero status.
+  Support for deployments to Rubygems is in alpha. Please see here: https://github.com/travis-ci/dpl/#maturity-levels
 
-#### Option:
+Options:
 
-* **script**: script to execute.
+  Either api_key, or user and password are required.
 
-#### Example:
+  --api_key KEY            Rubygems api key (type: string)
+  --username USER          Rubygems user name (type: string, alias: user)
+  --password PASS          Rubygems password (type: string)
+  --gem NAME               Name of the gem to release (type: string, default: repo name)
+  --gemspec FILE           Gemspec file to use to build the gem (type: string)
+  --gemspec_glob GLOB      Glob pattern to search for gemspec files when multiple gems are generated in the
+                           repository (overrides the gemspec option) (type: string)
+  --host URL               type: string
 
-    dpl --provider=script --script=./script/deploy.sh
+Common Options:
 
-### Google App Engine:
+  --run CMD                Command to execute after the deployment finished successfully (type: array
+                           (string, can be given multiple times))
+  --[no-]cleanup           Skip cleaning up build artifacts before the deployment
+  --help                   Get help on this command
 
-Deploys to Google App Engine and Google App Engine Managed VMs via the Google Cloud SDK and
-it's [`gcloud` tool](https://cloud.google.com/sdk/gcloud/) using a [Service Account](https://developers.google.com/console/help/new/#serviceaccounts).
-In order to use this provider, please make sure you have the [App Engine Admin API](https://developers.google.com/apis-explorer/#p/appengine/v1beta4/) enabled [in the Google Developers Console](https://console.developers.google.com/project/_/apiui/apiview/appengine/overview).
+Examples:
 
-#### Options:
+  dpl rubygems --api_key key
+  dpl rubygems --password pass
+  dpl rubygems --api_key key --username user --gem name --gemspec file --gemspec_glob glob
+```
 
-* **project**: [Project ID](https://developers.google.com/console/help/new/#projectnumber) used to identify the project on Google Cloud.
-* **keyfile**: Path to the JSON file containing your [Service Account](https://developers.google.com/console/help/new/#serviceaccounts) credentials in [JSON Web Token](https://tools.ietf.org/html/rfc7519) format. To be obtained via the [Google Developers Console](https://console.developers.google.com/project/_/apiui/credential). Defaults to `"service-account.json"`. Note that this file should be handled with care as it contains authorization keys.
-* **config**: Path to your module configuration file. Defaults to `"app.yaml"`. This file is runtime dependent ([Go](https://cloud.google.com/appengine/docs/go/config/appconfig), [Java](https://cloud.google.com/appengine/docs/java/configyaml/appconfig_yaml), [PHP](https://developers.google.com/console/help/new/#projectnumber), [Python](https://cloud.google.com/appengine/docs/python/config/appconfig))
-* **version**: The version of the app that will be created or replaced by this deployment. If you do not specify a version, one will be generated for you. See [`gcloud app deploy`](https://cloud.google.com/sdk/gcloud/reference/app/deploy)
-* **no_promote**: Flag to not promote the deployed version. See [`gcloud app deploy`](https://cloud.google.com/sdk/gcloud/reference/app/deploy)
-* **verbosity**: Let's you adjust the verbosity when invoking `"gcloud"`. Defaults to `"warning"`. See [`gcloud`](https://cloud.google.com/sdk/gcloud/reference/).
-* **no_stop_previous_version**: Flag to prevent your deployment from stopping the previously promoted version. This is from the future, so might not work (yet). See [`gcloud app deploy`](https://cloud.google.com/sdk/gcloud/reference/app/deploy)
+### Scalingo
 
-#### Environment variables:
+```
+Usage: dpl scalingo [options]
 
- * **GOOGLECLOUDPROJECT** or **CLOUDSDK_CORE_PROJECT**: Can be used instead of the `project` option.
- * **GOOGLECLOUDKEYFILE**: Can be used instead of the `keyfile` option.
+Summary:
 
-#### Example:
+  Scalingo deployment provider
 
-    dpl --provider=gae --project=example --no_promote=true
+Description:
 
-### Firebase:
+  tbd
 
-#### Options:
+  Support for deployments to Scalingo is in alpha. Please see here: https://github.com/travis-ci/dpl/#maturity-levels
 
-* **token**: Your Firebase CI access token (generate with `firebase login:ci`)
-* **project**: Deploy to a different Firebase project than specified in your `firebase.json` (e.g. `myapp-staging`)
-* **message**: Optional. The message describing this deploy.
+Options:
 
-#### Examples:
+  Either api_token, or username and password are required.
 
-    dpl --provider=firebase --token=<token> --project=<project> --message=<message>
+  --app APP              type: string, default: repo name
+  --api_token TOKEN      Scalingo API token (type: string, alias: api_key (deprecated, please use
+                         api_token))
+  --username NAME        Scalingo username (type: string)
+  --password PASS        Scalingo password (type: string)
+  --region REGION        Scalingo region (type: string, default: agora-fr1, known values: agora-fr1,
+                         osc-fr1)
+  --remote REMOTE        Git remote name (type: string, default: scalingo-dpl)
+  --branch BRANCH        Git branch (type: string, default: master)
+  --timeout SEC          Timeout for Scalingo CLI commands (type: integer, default: 60)
 
+Common Options:
 
+  --run CMD              Command to execute after the deployment finished successfully (type: array
+                         (string, can be given multiple times))
+  --[no-]cleanup         Skip cleaning up build artifacts before the deployment
+  --help                 Get help on this command
+
+Examples:
+
+  dpl scalingo --api_token token
+  dpl scalingo --username name --password pass
+  dpl scalingo --api_token token --app app --region agora-fr1 --remote remote --branch branch
+```
+
+### Script
+
+```
+Usage: dpl script [options]
+
+Summary:
+
+  Minimal provider that executes a custom command
+
+Description:
+
+  This deployment provider executes a single, custom command. This is
+  usually a script that is contained in your repository, but it can be
+  any command executable in the build environment.
+
+  It is possible to pass arguments to a script deployment like so:
+
+    dpl script -s './scripts/deploy.sh production --verbose'
+
+  Deployment will be marked a failure if the script exits with nonzero
+  status.
+
+  Support for deployments to Script is in alpha. Please see here: https://github.com/travis-ci/dpl/#maturity-levels
+
+Options:
+
+  -s --script SCRIPT      The script to execute (type: string, required: true)
+
+Common Options:
+
+  --run CMD               Command to execute after the deployment finished successfully (type: array
+                          (string, can be given multiple times))
+  --[no-]cleanup          Skip cleaning up build artifacts before the deployment
+  --help                  Get help on this command
+
+Examples:
+
+  dpl script --script script
+  dpl script --script script --run cmd --cleanup
+```
 
 ### Snap
 
-Deploys built snaps to the [snap store](https://snapcraft.io/).
+```
+Usage: dpl snap [options]
+
+Summary:
+
+  Snap deployment provider
 
-#### Options:
+Description:
 
-* **snap** Path (glob) of the snap to be pushed
-* **channel** Optional. Channel into which the snap will be released (defaults to `edge`)
-* **token** Optional. Login token for the store (generate with `snapcraft export-login`). Falls back to the `$SNAP_TOKEN` environment variable
+  tbd
+
+  Support for deployments to Snap is in development. Please see here: https://github.com/travis-ci/dpl/#maturity-levels
+
+Options:
+
+  --token TOKEN       Snap API token (type: string, required: true)
+  --snap STR          Path to the snap to be pushed (can be a glob) (type: string, default: **/*.snap)
+  --channel CHAN      Channel into which the snap will be released (type: string, default: edge)
+
+Common Options:
+
+  --run CMD           Command to execute after the deployment finished successfully (type: array
+                      (string, can be given multiple times))
+  --[no-]cleanup      Skip cleaning up build artifacts before the deployment
+  --help              Get help on this command
+
+Examples:
+
+  dpl snap --token token
+  dpl snap --token token --snap str --channel chan --run cmd --cleanup
+```
 
-#### Examples:
+### Surge
+
+```
+Usage: dpl surge [options]
+
+Summary:
+
+  Surge deployment provider
+
+Description:
+
+  tbd
+
+  Support for deployments to Surge is in alpha. Please see here: https://github.com/travis-ci/dpl/#maturity-levels
+
+Options:
+
+  --login EMAIL       Surge login (the email address you use with Surge) (type: string, required:
+                      true)
+  --token TOKEN       Surge login token (can be retrieved with `surge token`) (type: string, required:
+                      true)
+  --domain NAME       Domain to publish to. Not required if the domain is set in the CNAME file in the
+                      project folder. (type: string)
+  --project PATH      Path to project directory relative to repo root (type: string, default: .)
+
+Common Options:
+
+  --run CMD           Command to execute after the deployment finished successfully (type: array
+                      (string, can be given multiple times))
+  --[no-]cleanup      Skip cleaning up build artifacts before the deployment
+  --help              Get help on this command
+
+Examples:
+
+  dpl surge --login email --token token
+  dpl surge --login email --token token --domain name --project path --run cmd
+```
+
+### TestFairy
+
+```
+Usage: dpl testfairy [options]
+
+Summary:
+
+  TestFairy deployment provider
+
+Description:
+
+  Support for deployments to TestFairy is in alpha. Please see here: https://github.com/travis-ci/dpl/#maturity-levels
+
+Options:
+
+  --api_key KEY                       TestFairy API key (type: string, required: true)
+  --app_file FILE                     Path to the app file that will be generated after the build (APK/IPA) (type:
+                                      string, required: true)
+  --symbols_file FILE                 Path to the symbols file (type: string)
+  --testers_groups GROUPS             Tester groups to be notified about this build (type: string, e.g.: e.g.
+                                      group1,group1)
+  --[no-]notify                       Send an email with a changelog to your users
+  --[no-]auto_update                  Automaticall upgrade all the previous installations of this app this version
+  --advanced_options OPTS             Comma_separated list of advanced options (type: string, e.g.: option1,option2)
+
+Common Options:
+
+  --run CMD                           Command to execute after the deployment finished successfully (type: array
+                                      (string, can be given multiple times))
+  --[no-]cleanup                      Skip cleaning up build artifacts before the deployment
+  --help                              Get help on this command
+
+Examples:
+
+  dpl testfairy --api_key key --app_file file
+  dpl testfairy --api_key key --app_file file --symbols_file file --testers_groups groups --notify
+```
+
+### Transifex
+
+```
+Usage: dpl transifex [options]
 
-    dpl --provider=snap --token=<token> --snap=my.snap --channel=edge
+Summary:
 
+  Transifex deployment provider
 
+Description:
 
-### Surge.sh
+  tbd
 
-#### Options:
+  Support for deployments to Transifex is in alpha. Please see here: https://github.com/travis-ci/dpl/#maturity-levels
 
-* **project** Path to project folder relative to repo root. Defaults to repo root if not set.
-* **domain** Domain to publish to. Can be omitted if domain is set in the `CNAME` file in the project folder.
+Options:
 
+  Either api_token, or username and password are required.
+
+  --api_token TOKEN      Transifex API token (type: string)
+  --username NAME        Transifex username (type: string)
+  --password PASS        Transifex password (type: string)
+  --hostname NAME        Transifex hostname (type: string, default: www.transifex.com)
+  --cli_version VER      CLI version to install (type: string, default: >=0.11)
+
+Common Options:
+
+  --run CMD              Command to execute after the deployment finished successfully (type: array
+                         (string, can be given multiple times))
+  --[no-]cleanup         Skip cleaning up build artifacts before the deployment
+  --help                 Get help on this command
+
+Examples:
+
+  dpl transifex --api_token token
+  dpl transifex --username name --password pass
+  dpl transifex --api_token token --hostname name --cli_version ver --run cmd --cleanup
+```
+
+## Contributing to Dpl
+
+### Table of Contents
+
+* [Resources](#resources)
+* [Navigating the Codebase](#navigating-the-codebase)
+* [Lifecycle of the Deployment Process](#lifecycle-of-the-deployment-process)
+* [Deployment Tooling](#deployment-tooling)
+* [Runtime Dependencies](#runtime-dependencies)
+* [Unit Tests](#unit-tests)
+* [Runtime Dependency Installation Tests](#runtime-dependency-installation-tests)
+* [Integration Tests](#integration-tests)
+* [Testing Dpl Branches or Forks on Travis CI](#testing-dpl-branches-or-forks-on-travis-ci)
+* [Code Conventions](#code-conventions)
+* [Naming Conventions](#naming-conventions)
+* [Updating the README](#updating-the-readme)
+
+Dpl is a central component in Travis CI, and has been around for a long time.
+
+This library always has been a community effort first. There probably is not a
+single person in the world who is very familiar with all deployment providers
+supported by Dpl.
+
+*Thank you all for this!*
+
+This document is for you if you are looking to contribute to dpl, be it by
+adding a new deployment provider, fixing a bug, or adding a new feature.
+
+Dpl has a [code of conduct](CODE_OF_CONDUCT.md), please follow it in all
+interactions with the project.
+
+Dpl is written in Ruby, and we assume that you familiarize yourself with our
+documentation as much as needed.
+
+### Resources
+
+Hopefully helpful resources are:
+
+* This [document](CONTRIBUTING.md)
+* The [dpl README](README.md)
+* The [dpl API docs](https://www.rubydoc.info/github/travis-ci/dpl) on rubydocs.info
+* The [cl README](https://github.com/svenfuchs/cl/blob/master/README.md)
+
+### Navigating the Codebase
+
+All provider specific classes live in [dpl/providers](lib/dpl/providers).
+These represent the CLI commands that are executed when the command line
+exectuable `dpl` is run with a given provider name as the first argument.
+
+Each provider is a subclass of `Dpl::Provider`, which is defined in
+[dpl/provider.rb](lib/dpl/provider.rb). The provider base class itself
+subclasses from `Cl::Cmd`, so it represents an executable sub command of the
+main command `dpl`.
+
+For instance, the command `dpl s3 --bucket bucket` instantiates and runs the
+provider class [S3](lib/dpl/providers/s3.rb).
+
+The class `Cl::Cmd` contributes the command line options parser, and its
+class level DSL. Please see the [cl README](https://github.com/svenfuchs/cl/blob/master/README.md)
+for this DSL, and the [S3 provider](/lib/dpl/provider/s3.rb)
+for an example how dpl uses it.
+
+The class `Dpl::Provider` adds, amongst other things, the order of stages
+(methods) that make up the deployment process:
+
+* `init`
+* `install`
+* `login`
+* `setup`
+* `validate`
+* `prepare`
+* `deploy`
+* `finish`
+
+Implementors of concrete provider classes may or may not choose to implement
+any of these instance methods according to their needs, and semantics of their
+tooling and service providers. Please refer to [Dpl::Provider](/lib/dpl/provider.rb)
+for details.
+
+The DSL that is used to declare features, dependencies, environment integration
+etc. on the concrete provider classes is defined in the module
+`Dpl::Provider::DSL`, in [dpl/provider/dsl](/lib/dpl/provider/dsl.rb).
+
+Also of interest is [Dpl::Ctx::Bash](/lib/dpl/ctx/bash.rb),
+the Bash execution context, that runs shell commands, installs dependencies
+etc. (while the `Test` context class is used for testing in order to keep your
+development machine clean and safe when you run tests locally).
+
+```
+lib
+└── dpl
+    ├── assets                # Stores larger shell scripts
+    ├── ctx
+    │   ├── bash.rb           # Bash execution context
+    │   └── test.rb           # Test execution context
+    ├── provider.rb           # Base class for all providers
+    ├── provider
+    │   ├── dsl.rb            # DSL for defining providers
+    │   └── example.rb        # Generating example commands for help output
+    └── providers
+        ├── anynines.rb       # Concrete providers
+        ├── atlas.rb
+        ├── azure_webapps.rb
+        ├── bintray.rb
+        ├── bitballoon.rb
+        └── ⋮
+```
+
+### Lifecycle of the Deployment Process
+
+When a provider class is instantiated and run it will go through a number
+of stages that make up the deployment process.
+
+These are documented in [dpl/provider.rb](/lib/dpl/provider.rb).
+If you are adding a new deployment provider please familiarize youself with
+this lifecycle.
+
+Feel free to pick and interpret these stages according to the needs and
+semantics of the service provider you are adding. By no means do all of these
+stages have to be filled in or implmented. The `Provider` base class checks for
+these methods, and runs them, if present, so that implementors can choose
+semantically fitting names for their providers.
+
+### Deployment Tooling
+
+If you are adding a new deployment provider please choose the tooling you are
+going to use carefully.
+
+Dpl is a long lived library, and it has outlived many tools that once were
+supported, and no longer are. Thus tooling stability is a major concern for
+this project.
+
+Ideally use official CLI tooling supported by the company who's service
+provider you are about to add. Often, such CLI tools can be installed via
+standard package managers, or manually downloaded using `curl` and installed
+with a few simple Bash commands.
+
+Such CLI tooling is preferrable over Ruby gem runtime dependencies as they can
+be executed in a child process, and won't introduce any dependency resolution
+problems later on.
+
+If no such CLI is available, or it does not look well supported, and your
+provider implementation needs to talk to an external HTTP API then please consider
+using [Net::HTTP](https://ruby-doc.org/stdlib-2.6.3/libdoc/net/http/rdoc/Net/HTTP.html)
+from Ruby's standard library.
+
+If you absolutely have to rely on a runtime Ruby gem dependency, such as a
+provider client implementation, please only do so if the gem is supported by
+the respective company officially. We may choose to reject including runtime
+dependencies that do not look stable or widely supported.
+
+### Runtime Dependencies
+
+Runtime dependencies can be declared on the provider class using the
+[DSL](lib/dpl/provider/dsl.rb).
+
+In the case of APT, NPM, and Pip dependencies these will be installed via
+shell commands at the beginning of the deployment process.
+
+Ruby gem dependencies will be installed using Bundler's [inline API](https://github.com/bundler/bundler/blob/master/lib/bundler/inline.rb),
+at the beginning of the deployment process, so they are available in the same
+Ruby process from then on.
+
+### Unit Tests
+
+`Dpl` uses [RSpec](https://github.com/rspec) for tests. The specs reside in
+`spec`, and each provider class has a corresponding file
+`spec/dpl/providers/*_spec.rb` to hold tests.
+
+Provider tests should be implemented on an input/output acceptance level, as
+much as possible.
+
+They use a [Ctx::Test](blob/masterlib/dpl/ctx/test.rb) execution context in
+order to avoid running actual shell commands, or actually installing
+dependencies at test time. There are custom [RSpec matchers](spec/support/matchers)
+in place that help with making assertions against this execution context.
+
+If your provider has to talk to an external HTTP API then ideally use
+[Webmock](https://github.com/bblimke/webmock) to stub external requests. If by
+any means possible try to avoid mocking or stubbing Ruby client classes (this
+is not always possible, but should be considered).
+
+#### Running Unit Tests Locally
+
+You can run the unit test suite locally as follows:
+
+```
+bundle install
+bundle exec rspec
+```
+
+In order to execute tests only for a certain provider you can run:
+
+```
+bundle exec rspec spec/dpl/providers/[provider]_spec.rb
+```
+
+In order to execute a single test or group of tests add a line number like so:
+
+```
+bundle exec rspec spec/dpl/providers/[provider]_spec.rb:25
+```
+
+These tests can be run safely on any development machine, anywhere.
+
+### Runtime Dependency Installation Tests
+
+We additionally run tests that exercise runtime dependency installation on
+Travis CI.
+
+These live in [.travis/test_install.rb](.travis/test_install.rb). It is not
+advisable to run these tests outside of an ephemeral VM or container that can
+be safely discarded, as they are going to leave various artifacts around.
+
+### Integration Tests
+
+In order to ensure proper integration with the service providers supported
+we also periodically run a test suite that exercises actual deployments to
+these providers.
+
+These tests live in [.travis/providers](/.travis/providers), and the are
+triggered using the script [trigger](/.travis/trigger).
+
+An integration test consists of:
+
+* A setup script that creates an application (or artifact) to deploy (or
+  upload).
+* A YAML config snippet that configures and triggers the deployment as part of
+  a build on Travis CI.
+* A test script that tests if the deployment was successful.
+
+For example:
+
+* [github-pages/prepare](/.travis/providers/github-pages/prepare)
+  creates a minimal Git repository that serves an `index.html` on GitHub Pages in a temporary directory.
+* [github-pages/travis.yml](/.travis/providers/github-pages/travis.yml)
+  configures the build to use Dpl 2.0 to deploy this repository to GitHub Pages.
+* [github-pages/test](/.travis/providers/github-pages/test)
+  tests if the deployment was successful.
+
+The tests can be run on Travis CI individually, or combined, by triggering a
+build via our API, using the script [.travis/trigger](/.travis/trigger).
+This takes a provider name as an argument, and requires a Travis CI API token.
+
+For example, this triggers a build that executes the GitHub Pages test on
+Travis CI:
+
+```
+.travis/trigger github-pages --token [token]
+```
+
+The token can also be set as an environment variable:
+
+```
+export TRAVIS_API_TOKEN=[token]
+.travis/trigger github-pages
+```
+
+The `trigger` script accepts multiple provider names as arguments. If no
+arguments are given then tests for all providers will be run.
+
+#### Integration Test Configuration
+
+In the build config YAML snippet make sure to use the branch of your fork for the
+deployment tooling, and allow the deployment to run on your branch:
+
+```yaml
+deploy:
+  - provider: [name]
+    edge:
+      source: [your-login]/dpl
+      branch: [your-branch]
+    on:
+      branch: [your-branch]
+```
+
+Ideally use credentials for an isolated account on the service you are deploying to.
+This is generally good practice, and way you can hand things off to someone else.
+
+In order to get things working encrypt the credentials against your fork, and
+add them to the build config YAML snippet. If you are in the root directory
+of your fork then this command should do the trick:
+
+```
+travis encrypt password=[password]
+```
+
+If you do not have the `travis` CLI installed you can install it using:
+
+```
+gem install travis
+```
+
+When you add encrypted credentials to the build config YAML snippet also add a comment
+that allows others to identify the account used. E.g:
+
+```yaml
+deploy:
+  - provider: pages
+    github_token:
+      # personal access token with repo scope on the account [name]
+      secure: "[encrypted token]"
+```
+
+Open a pull request. In order for us to merge your test, and get it working on
+our repository you will need to re-encrypt the credentials against
+`travis-ci/dpl`, like so:
+
+```
+travis encrypt -r travis-ci/dpl password=[password]
+```
+
+Whatever minimal deployment you can get working is be a great contribution.
+Even if for some reason it proves hard to test the deployment in an automated
+fashion, but you have a successful deployment that can be verified manually,
+please still open a pull request, and talk to us. Any test is better than no
+test.
+
+### Testing Dpl Branches or Forks on Travis CI
+
+It is possible to test a new deployment provider or new functionality of dpl on
+Travis CI. In order to do so, add proper configuraiton on the `edge` key to
+your `.travis.yml` like so:
+
+```yaml
+deploy:
+  provider: [name]
+  edge:
+    source: [github-handle]/dpl
+    branch: [branch]
+  on:
+    branch: TEST_BRANCH # or all_branches: true
+  ⋮ # rest of your provider's configuration
+```
+
+This builds the `dpl` gem on the Travis CI build environment from your
+repository, on the given branch. Then it installs the gem built from this code
+base, and uses it to run your deployment.
+
+When submitting a pull request, please be sure to run at least one deployment
+with the new configuration, and provide a link to the build in your pull
+request.
+
+### Code Conventions
+
+Dpl does not follow any strict code styleguide.
+
+Please take a look around other providers, and try to follow a similar code
+style to what you find.
+
+Try to use the [DSL](/lib/dpl/provider/dsl.rb) as much
+as possible.  It keeps the code declarative and readable, so that people not
+familiar with Ruby or programming in general can still follow it, and make
+sense of it.
+
+If you find yourself trying to achieve something that should be, but is not
+supported by the DSL please [open an issue](https://github.com/travis-ci/dpl/issues/new)
+about it.
+
+If you are rather unfamiliar with Ruby, and have trouble following our code
+style then please submit your pull request anyway, or get in touch, so we can
+help.
+
+### Naming Conventions
+
+Dpl uses constant names following Ruby naming conventions. I.e. constant
+names use `CamelCase`, and they live in files named in `snake_case.rb`.
+
+If you pick such names for a new provider please try to follow these
+conventions.
+
+Real world service provider or company names do not always translate to such
+conventional Ruby names one-to-one. That is ok, they don't have to. These Ruby
+constant names are representations of real world service and company names in
+Ruby code.
+
+Other Ruby libraries often (not always) follow a similar thinking. E.g.
+even though Amazon Web Services brand name is `AWS` the module name
+they chose in their [aws-sdk](https://github.com/aws/aws-sdk-ruby) is
+`Aws`, not `AWS`.
+
+### Updating the README
+
+The [README](/README.md) is generated from a
+[template](/lib/dpl/assets/dpl/README.erb.md).
+
+In order to update the README please edit the template, and run:
+
+```
+gem install ffi-icu
+bin/readme > README.md
+```
 
-#### Environment variables:
 
-* **SURGE_LOGIN**: Set it to the email address you use with Surge
-* **SURGE_TOKEN**: Set it to your login token (get it by doing a `surge token`)
+## Old Issues
 
-#### Example:
-    dpl --provider=surge --project=<project-path> --domain=<domain-name>
+If an issue has been left open and untouched for 90 days or more, we
+automatically close them. We do this to ensure that new issues are more easily
+noticeable, and that old issues that have been resolved or are no longer
+relevant are closed. You can read more about this [here](https://blog.travis-ci.com/2018-03-09-closing-old-issues).
 
-### Bluemix Cloud Foundry:
+## Code of Conduct
 
-#### Options:
+Please see [our code of conduct](CODE_OF_CONDUCT.md) for how to interact with
+this project and its community.
 
-* **username**: Bluemix username.
-* **password**: Bluemix password.
-* **organization**: Bluemix target organization.
-* **space**: Bluemix target space
-* **region**: Bluemix region [ng, eu-gb, eu-de, au-syd]. Optional, default US region (ng).
-* **api**: Bluemix api URL. Optional for Bluemix dedicated. Explicit **api** setting precedence over **region** setting.
-* **app_name**: Application name. Optional.
-* **manifest**: Path to manifest file. Optional.
-* **skip_ssl_validation**: Skip ssl validation. Optional.
+## License
 
-#### Examples:
+Dpl is licensed under the [MIT License](https://github.com/travis-ci/dpl/blob/master/LICENSE).
 
-    dpl --provider=bluemixcloudfoundry --username=<username> --password=<password> --organization=<organization> --region=<region> --space=<space> --skip-ssl-validation
+## Credits
 
-## `dpl` and `sudo`
+This tool would not exist without your help.
 
-`dpl` installs deployment provider code as the user invoking
-`dpl` at run time, if it is not available.
-This causes [a problem](https://github.com/travis-ci/dpl/issues/769)
-if you invoke `dpl` via `dpl`, where the process instaling the
-provider code may not have sufficient permissions.
+A huge thank you goes out to all of our current and past [contributors](https://github.com/travis-ci/dpl/graphs/contributors):
 
-In this case, you can install the provider gem (of the same version as
-`dpl`) with `sudo` beforehand to work around this issue.
+5c077yP, A.J. May, A92hm, Aakriti Gupta, Aaron Hill, Aaron1011, Abdón Rodríguez Davila, Adam King, Adam Mcgrath, adinata, Adrian Moreno, Ahmad Nassri, Ahmed Refaey, Ainun Nazieb, Albertin Loic, Alexander Springer, Alexey Kotlyarov, Ali Hajimirza, Amos Wenger, Anders Olsen Sandvik, Andrey Lushchick, Andy Vanbutsele, Angelo Livanos, Anne-Julia Seitz, Antoine Savignac, Anton Babenko, Anton Ilin, Arnold Daniels, Ashen Gunaratne, awesomescot, Axel Fontaine, Baptiste Courtois, Ben Hale, Benjamin Guttmann, Bob, Bob Zoller, Brad Gignac, Brandon Burton, Brandon LeBlanc, Brian Hou, Cameron White, capotej, Carla, carlad, Chad Engler, Chathan Driehuys, Christian Elsen, Christian Rackerseder, Clay Reimann, cleem, Cryptophobia, Damien Mathieu, Dan Buch, Dan Powell, Daniel X Moore, David F. Severski, Denis Cornehl, Dennis Koot, Devin J. Pohly, Dominic Jodoin, Dwayne Forde, emdantrim, Eric Peterson, Erik Dalén, Esteban Santiesteban, Étienne Michon, eyalbe4, Fabio Napoleoni, Felix Rieseberg, fgogolli, Filip Š, Flamur Gogolli, Gabriel Saldana, George Brighton, Gil, Gil Megidish, Gil Tselenchuk, Hao Luo, Hauke Stange, Henrik Hodne, Hiro Asari, IMANAKA, Kouta, Ivan Evtuhovich, Ivan Kusalic, Ivan Pozdeev, Jacob Burkhart, Jake Hewitt, Jakub Holy, James Adam, James Awesome, James Parker, Janderson, Jannis Leidel, Jeffrey Yasskin, Jeremy Frasier, Joe Damato, Joep van Delft, Johannes Würbach, johanneswuerbach, Johnny Dobbins, Jon Benson, Jon Rowe, Jon-Erik Schneiderhan, Jonatan Männchen, Jonathan Stites, Jonathan Sundqvist, jorgecasar, Josh Kalderimis, joshua-anderson, Jouni Kaplas, Julia S.Simon, Julio Capote, jung_b@localhost, Karim Fateem, Ke Zhu, konrad-c, Konstantin Haase, Kouta Imanaka, Kristofer Svardstal, Kyle Fazzari, Kyle VanderBeek, Loïc Mahieu, Lorenz Leutgeb, Lorne Currie, Louis Lagrange, Louis St-Amour, Luke Yeager, Maciej Skierkowski, María de Antón, mariadeanton, Mariana Lenetis and Zachary Gershman, Marius Gripsgard, Mark Pundsack, marscher, Marwan Rabbâa, Mathias Meyer, Mathias Rangel Wulff, Mathias San Miguel, Matt Hernandez, Matt Knox, Matt Travi, Matthew Knox, Maxime Brugidou, mayeut, Meir Gottlieb, Michael Bleigh, Michael Dunn, Michael Friis, Michel Boudreau, Mike Bryant, Nat Welch, Nicholas Bruning, Nick Mohoric, Nico Lindemann, Nigel Ramsay, Ole Michaelis, Omer Katz, Patrique Legault, Paul Beaudoin, Paul Nikitochkin, Peter, Peter Georgantas, Peter Newman, Philipp Hansch, Piotr Sarnacki, Rail Aliiev, Randall A. Gordon, Robert Gogolok, Rokas Brazdžionis, Romuald Bulyshko, ryanj, Ryn Daniels, Samir Talwar, Samuel Wright, Sandor Zeestraten, SAULEAU Sven, Scot Spinner, Sebastien Estienne, Sergei Chertkov, shunyi, Simon, Solly, Sorin Sbarnea, Soulou, Stefan Kolb, Steffen Kötte, step76, Steven Berlanga, Sven Fuchs, Sviatoslav Sydorenko, testfairy, Tim Ysewyn, Troels Thomsen, Tyler Cross, Uriah Levy, Vincent Jacques, Vojtech Vondra, Vojtěch Vondra, Wael M. Nasreddine, Wim Looman, Xavier Krantz, yeonhoyoon, Zane Williamson