Building a Go Project

What This Guide Covers

This guide covers build environment and configuration topics specific to Go projects. Please make sure to read our Getting Started and general build configuration guides first.

Go builds are not available on the OS X environment.

CI environment for Go Projects

Travis CI VMs are 64 bit and currently provide

  • recent versions of Go
  • core GNU build toolchain (autotools, make), cmake, scons

Go projects on assume you use Make or straight Go build tool by default.

Specifying a Go version to use

You can use any tagged version of Go, a version with x in place of the minor or patch level to use the latest for a given major or minor version, or use master to get the latest version from source.

language: go

  - 1.x
  - 1.6
  - 1.7.x
  - master

All go version management is handled by gimme.

For precise versions pre-installed on the VM, please consult “Build system information” in the build log.

Go Import Path

The project source code will be placed in GOPATH/src/ by default, but if vanity imports are necessary (especially for internal package imports), go_import_path: may be specified at the top level of the config, e.g.:


Dependency Management

By default the install step defers to go get ./... or go get -t ./... if the version of go is greater than or equal to 1.2. If any of the following files are present, the default install step will be simply true:

  • GNUMakefile
  • Makefile
  • BSDmakefile
  • makefile

If you need to perform special tasks before your tests can run, override the install: key in your .travis.yml:

install: make get-deps

It is also possible to specify a list of operations, for example, to go get remote dependencies:

  - go get
  - go get

See general build configuration guide to learn more.

godep support

There is support included for godep when used with vendored dependencies such that the GOPATH will be prefixed with ${TRAVIS_BUILD_DIR}/Godeps/_workspace and PATH will be prefixed with ${TRAVIS_BUILD_DIR}/Godeps/_workspace/bin. Additionally, if the Godeps/_workspace/src directory does not exist, godep will be installed and a godep restore will be run.

It is important to note that using the older style Godeps.json at the top level is not supported.

All of the godep integration steps are performed prior to the separate go get and makefile steps listed above.

Note that the godep support is only activated if a custom install step is not specified.

Installing Private Dependencies

As go get uses HTTPS to clone dependencies from GitHub rather than SSH, it requires a different workaround from our recommended way of handling private dependencies.

When cloning via HTTPS, git uses curl under the covers, which in turn allows you to specify a .netrc file, where you can store custom authentication credentials for specific domains, for instance.

Go to your GitHub account and create a personal access token.

Screenshot of GitHub personal token

Make sure to give it the repo scope, which allows accessing private repositories.

To reduce access rights of the token, you can also create a separate user account with access to only the repositories you need for a particular project.

Copy the token and store it in a .netrc in your repository, with the following data:

  login <username>
  password <token>

Add this to your repository and add the following steps to your .travis.yml:

  - cp .netrc ~
  - chmod 600 .netrc

You can leave out the second step if your .netrc already has access permissions set only for the owner. That’s a requirement for it to be read from curl.

Default Test Script

Go projects on assume that either Make or Go build tool are used by default. In case there is a Makefile in the repository root, the default command Travis CI will use to run your project test suite is


In case there is no Makefile, it will be

go test -v ./...


Projects that find this sufficient can use a very minimalistic .travis.yml file:

language: go

This can be overridden as described in the general build configuration guide. For example, to omit the -v flag, override the script: key in .travis.yml like this:

script: go test ./...

The arguments passed to the default go test command may be overridden by specifying gobuild_args: at the top level of the config, e.g.:

gobuild_args: -x -ldflags "-X main.VersionString v1.2.3"

which will result in the script step being:

go test -x -ldflags "-X main.VersionString v1.2.3" ./...

To build by running Scons without arguments, use this:

script: scons

Build Matrix

For Go projects, env and go can be given as arrays to construct a build matrix.

Environment Variable

The version of Go a job is using is available as:


Please note that this will expand to the real Go version, for example 1.7.4, also when go: 1.7.x was specified. Comparing this value in for example the deploy section could look like this:

    condition: $TRAVIS_GO_VERSION =~ ^1\.7\.[0-9]+$