Netlify Drop Deployment
This page documents deployments using the next major version dpl v2 which currently is in a beta release phase. Please see our blog post for details. The current default version is dpl v1. Check dpl v1 documentation here.
Travis CI can automatically deploy files to Netlify Drop after a successful build.
For a minimal configuration, add the following to your
deploy: provider: netlify site: <site> auth: <encrypted auth> edge: true # opt in to dpl v2
Support for deployments to Netlify is *stable**.
Known options #
Use the following options to further configure the deployment.
||A site ID to deploy to — required, type: string|
||An auth token to log in with — required, secret, type: string|
||Specify a folder to deploy — type: string|
||Specify a functions folder to deploy — type: string|
||A message to include in the deploy log — type: string|
||Deploy to production — type: boolean|
Shared options #
||Clean up build artifacts from the Git working directory before the deployment — type: boolean|
||Commands to execute after the deployment finished successfully — type: string or array of strings|
Environment variables #
All options can be given as environment variables if prefixed with
auth can be given as
Securing secrets #
Secret option values should be given as either encrypted strings in your build
.travis.yml file) or environment variables in your repository
Environment variables can be set on the settings page of your repository, or
travis env set:
travis env set NETLIFY_AUTH <auth>
In order to encrypt option values when adding them to your
travis encrypt <auth>
--add to directly add it to your
.travis.yml file. Note that this command has to be run in your repository’s root directory:
travis encrypt --add deploy.auth <auth>
Deploying a specific directory #
To deploy a specific directory, use the
deploy: provider: netlify # ⋮ dir: "_build/"
Pull Requests #
Note that pull request builds skip the deployment step altogether.