Skip to content
This repository was archived by the owner on May 9, 2021. It is now read-only.

Update travis for go1.8 + tip #277

Merged
merged 1 commit into from
Feb 26, 2017
Merged

Update travis for go1.8 + tip #277

merged 1 commit into from
Feb 26, 2017

Conversation

cblecker
Copy link
Contributor

Update golint testing to use go1.8 and to test against tip (but permit failures)

@dsnet dsnet merged commit df5f241 into golang:master Feb 26, 2017
@dsnet
Copy link
Member

dsnet commented Feb 26, 2017

Thanks for the PR. It's good to be testing on the latest.

@cblecker cblecker deleted the travis-1.8 branch February 26, 2017 03:32
@dmitshur
Copy link
Member

dmitshur commented Feb 28, 2017

Travis still supports tip for backwards compatibility, but it's better to use master because that's what their documentation covers.

See https://docs.travis-ci.com/user/languages/go#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.

Edit: I've made #279 that implements the minor improvement above, plus a few other enhancements that I'm familiar with, for your consideration.

dsnet pushed a commit that referenced this pull request Feb 28, 2017
… -race. (#279)

* Update .travis.yml for latest conventions, use fast_finish, test with -race.

This change follows #277, but updates .travis.yml to use latest
conventions as documented at https://docs.travis-ci.com/user/languages/go#Specifying-a-Go-version-to-use.
Specifically, use master instead of tip to refer to latest (unreleased)
version of Go.

Use .x to target latest patch releases of each point release of Go.

Use fast_finish to speed up build reporting with no semantic change.
It's documented at https://blog.travis-ci.com/2013-11-27-fast-finishing-builds/.

Use race detector when running tests.

* Update .travis.yml to migrate from legacy to container-based infrastructure.

If lint doesn't do anything that would require sudo access,
it's a good idea not to require sudo access. This allows the builds
to run on Travis' newer container-based infrastructure, which
are not considered legacy and should run faster.
See https://docs.travis-ci.com/user/migrating-from-legacy/ for details.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants