Contents

# Testing `dpl` in the context of Travis CI builds

It is possible to test new deployment provider or new functionality
of dpl when it is used from the Travis CI build script.

To do so, add the following to your `.travis.yml`:

```yaml
deploy:
  provider: X
  edge:
  	source: myown/dpl
    branch: foo
  on:
  	branch: TEST_BRANCH # or all_branches: true
  ⋮ # rest of provider X configuration
```

This builds the `dpl` gem on the VM
from `https://github.com/myown/dpl`, the `foo` branch.
Then it installs the locally built gem,
and uses that to deploy.

Notice that this is not a merge commit, so it is important
that when you are testing your PR, the branch `foo` is up-to-date
with https://github.com/travis-ci/dpl/tree/master/.

When opening a PR, be sure to run at least one deployment with the new configuration,
and provide a link to the build in the PR.

Version data entries

114 entries across 114 versions & 1 rubygems

Version	Path
dpl-1.8.33.travis.2025.5	TESTING.md
dpl-1.8.33.travis.1999.5	TESTING.md
dpl-1.8.33.travis.1976.5	TESTING.md
dpl-1.8.32	TESTING.md
dpl-1.8.32.travis.1958.5	TESTING.md
dpl-1.8.32.travis.1957.5	TESTING.md
dpl-1.8.32.travis.1956.5	TESTING.md
dpl-1.8.32.travis.1955.5	TESTING.md
dpl-1.8.32.travis.1950.5	TESTING.md
dpl-1.8.32.travis.1949.5	TESTING.md
dpl-1.8.32.travis.1935.5	TESTING.md
dpl-1.8.32.travis.1901.6	TESTING.md
dpl-1.8.32.travis.1900.4	TESTING.md
dpl-1.8.32.travis.1899.3	TESTING.md
dpl-1.8.31.travis.1897.3	TESTING.md
dpl-1.8.31.travis.1898.3	TESTING.md
dpl-1.8.31	TESTING.md
dpl-1.8.31.travis.1895.3	TESTING.md
dpl-1.8.31.travis.1892.3	TESTING.md
dpl-1.8.31.travis.1882.3	TESTING.md