Skip to content

Configure builds on Travis CI


Travis CI will not be enabled for any new environments. Environments already set up with Travis CI can continue to use it with the caution that its support will be deprecated in the near future.

It is recommended to configure builds on CircleCI instead.

Begin by reading the Travis CI getting started documentation. Do not yet add the Travis CI config at this point.

  1. Visit, authenticate with your GitHub account, and add your repository to Travis CI
  2. Create or adapt a config for Travis CI:
    • If you have no Travis CI config in your repository, copy this config to .travis.yml in your repo; you will need to add the build command(s) you’re using in the section under “@TODO: Configure build steps”
    • If you already have a config, you’ll need to:
      1. Add the build command(s), referencing the before_script section in our example config commented with “@TODO: Configure build steps”
      2. Add the two sets of two lines referenced by the “REQUIRED:” comments
  3. Ensure you have a machine user, this is a regular GitHub user account which is used purely for scripted functions, e.g. used by Travis CI to commit and push the built code (GitHub call this user a “machine user”):
    • If you have no dedicated “machine user” account, create a new GitHub account, named appropriately.
    • If you already have a machine user for your team, then use that account for the following steps.
  4. Setup a key pair for your machine user:
    1. Use the command line on your local machine to create a public private key pair (documentation)
    2. Set the public portion of the key pair as a deploy key with write permissions on the GitHub repository (documentation)
    3. Add the private key as a setting on your Travis repository (see “Adding a deploy key in repository settings on Travis CI” below)
  5. If necessary, add and update a .deployignore file.
  6. Merge a PR to the production branch… it should be built by Travis CI, committed to your production-built branch, and pushed up to GitHub (verify the branch now exists on GitHub and contains the changes you made)
  7. Contact VIP Support to request that the production-built branch deploys to the environment.

Adding a deploy key as a repository variable on Travis CI


Read these instructions through completely before executing the steps.

  1. Add the public portion of the key as a deploy key on your GitHub repository; GitHub documentation on deploy keys.
  2. Set the private portion of the key as a repository variable in the Travis settings. You will need to replace newlines with \n and surround it with double quotes, e.g. “THIS\nIS\A\KEY\nABC\n123\n”; Travis documentation on repository variables in settings.
  3. You must set the “Display value in build log” toggle for the repository variable to “off”.
  4. You must name the Travis setting that contains the key BUILT_BRANCH_DEPLOY_KEY.

Last updated: August 03, 2023

Relevant to

  • Node.js
  • WordPress