Use .go-version to specify the Go version for all CI builds #4303
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Having a simple file that requires no parsing to retrieve the Go version provides us a standard portable way to know what Go version to use for builds. It's basically the least common denominator for builds accross CI systems (Jenkins, AppVeyor, Travis) and operating systems. Also changed AppVeyor to invalidate the cached Go version only when the .go-version file changes instead of when the .appveyor.yml changes.
ruflin
approved these changes
May 12, 2017
|
WFG |
glefloch
approved these changes
May 13, 2017
andrewkroh
added a commit
to andrewkroh/beats
that referenced
this pull request
May 13, 2017
…4303) Having a simple file that requires no parsing to retrieve the Go version provides us a standard portable way to know what Go version to use for builds. It's basically the least common denominator for builds accross CI systems (Jenkins, AppVeyor, Travis) and operating systems. Also changed AppVeyor to invalidate the cached Go version only when the .go-version file changes instead of when the .appveyor.yml changes.
ruflin
pushed a commit
that referenced
this pull request
May 13, 2017
…4307) Having a simple file that requires no parsing to retrieve the Go version provides us a standard portable way to know what Go version to use for builds. It's basically the least common denominator for builds accross CI systems (Jenkins, AppVeyor, Travis) and operating systems. Also changed AppVeyor to invalidate the cached Go version only when the .go-version file changes instead of when the .appveyor.yml changes.
andrewkroh
added a commit
to andrewkroh/beats
that referenced
this pull request
May 26, 2017
…4303) Having a simple file that requires no parsing to retrieve the Go version provides us a standard portable way to know what Go version to use for builds. It's basically the least common denominator for builds accross CI systems (Jenkins, AppVeyor, Travis) and operating systems. Also changed AppVeyor to invalidate the cached Go version only when the .go-version file changes instead of when the .appveyor.yml changes. (cherry picked from commit 795ceab)
tsg
pushed a commit
that referenced
this pull request
May 29, 2017
…4403) Having a simple file that requires no parsing to retrieve the Go version provides us a standard portable way to know what Go version to use for builds. It's basically the least common denominator for builds accross CI systems (Jenkins, AppVeyor, Travis) and operating systems. Also changed AppVeyor to invalidate the cached Go version only when the .go-version file changes instead of when the .appveyor.yml changes. (cherry picked from commit 795ceab)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Having a simple file that requires no parsing to retrieve the Go version
provides us a standard portable way to know what Go version to use for builds.
It's basically the least common denominator for builds accross CI systems
(Jenkins, AppVeyor, Travis) and operating systems.
Also changed AppVeyor to invalidate the cached Go version only when the
.go-version file changes instead of when the .appveyor.yml changes.