Date: 2022-04-13
Status: Accepted
actions/setup-go
is the one of the most popular action related to Golang in GitHub Actions. Many customers use it in conjunction with actions/cache to speed up dependency installation process.
See more examples on proper usage in actions/cache documentation.
Integration of caching functionality into actions/setup-go
action will bring the following benefits for action users:
- Decrease the entry threshold for using the cache for Go dependencies and simplify initial configuration
- Simplify YAML pipelines because there will be no need for additional steps to enable caching
- More users will use cache for Go so more customers will have fast builds!
We don't pursue the goal to provide wide customization of caching in scope of actions/setup-go
action. The purpose of this integration is covering ~90% of basic use-cases. If user needs flexible customization, we should advice them to use actions/cache
directly.
- Add
cache
input parameter toactions/setup-go
. For now, input will accept the following values:true
- enable caching for go dependenciesfalse
- disable caching for go dependencies. This value will be set as default value
- Cache feature will be disabled by default to make sure that we don't break existing customers. We will consider enabling cache by default in next major releases
- Action will try to search a go.sum files in the repository and throw error in the scenario that it was not found
- The hash of found file will be used as cache key (the same approach like actions/cache recommends)
- The following key cache will be used
${{ runner.os }}-go${{ go-version }}-${{ hashFiles('<go.sum-path>') }}
- Action will cache global cache from the
go env GOMODCACHE
andgo env GOCACHE
commands. - Add a
cache-dependency-path
input parameter toactions/setup-go
. The new input will accept an array or regex of dependency files. The field will accept a path (relative to the repository root) to dependency files. If the provided path contains wildcards, the action will search all matching files and calculate a common hash like the ${{ hashFiles('**/go.sum') }} YAML construction does.
steps:
- uses: actions/checkout@v3
- uses: actions/setup-go@v3
with:
go-version: '18'
cache: true
- With cache-dependency-path
steps:
- uses: actions/checkout@v3
- uses: actions/setup-go@v3
with:
go-version: '18'
cache: true
cache-dependency-path: **/go.sum
steps:
- uses: actions/checkout@v3
- uses: actions/setup-go@v3
with:
go-version: '18'
cache: true
cache-dependency-path: |
**/go.sum
**/go.mod
steps:
- uses: actions/checkout@v3
- uses: actions/setup-go@v3
with:
go-version: '18'
cache: true
cache-dependency-path: **/go.sum
env:
GOOS: ...
GOARCH: ...
steps:
- run: echo "$GOOS $GOARCH"> /tmp/env
- uses: actions/setup-go@v4
with:
cache-dependency-path: go.sum /tmp/env
- uses: actions/setup-go@v4
with:
go-version: '1.20'
cache-dependency-path: go.sum **/*.go
If there are several builds on the same repo it might make sense to create a cache in one build and use it in the others. The action actions/cache/restore should be used in this case.
This advanced use case requires the use of actions/cache
This advanced use case assumes manual definition of cache key and requires the use of actions/cache
To avoid race conditions during the parallel builds they should either generate their own caches, or create the cache for only one build and restore that cache in the other builds.
As soon as functionality is implemented, we will release minor update of action. No need to bump major version since there are no breaking changes for existing users. After that, we will update starter-workflows