mirror of
https://github.com/hashicorp/vault.git
synced 2025-08-06 06:37:02 +02:00
0d8f1d30f3
* VAULT-36174: pipeline(go): Deal with relative path issues in cache restore Cache restore have some surprising relative pathing behavior we need to deal with. Since our Go module cache-path is in $HOME (/home/runner/go/...) and $HOME can be different depending on our self-hosted vs Github hosted runners (/home/runner/actions-runner/_work vs. /home/runner/work) we need to factor in the absolute path of $HOME when creating our cache key. If we don't then cache restores will be incompatible on one or the other runner. This is because the tar restore uses relative paths backwards our our depth doesn't match on both runners. We also slightly change our module caches here to only get `.../mod/cache` instead of the whole `.../mod` directory. Go is able to unzip the modules in cache faster than it takes a longer download with the entire mod directory. This will double our module caches *sigh* but they ought to be smaller as they only contain the module zips. See: https://github.com/actions/cache/issues/1127 Signed-off-by: Ryan Cragun <me@ryan.ec> * use working dir, not home Signed-off-by: Ryan Cragun <me@ryan.ec> * fix logic on no-save Signed-off-by: Ryan Cragun <me@ryan.ec> * do a module list after download Signed-off-by: Ryan Cragun <me@ryan.ec> --------- Signed-off-by: Ryan Cragun <me@ryan.ec> |
||
|---|---|---|
| .. | ||
| cross | ||
| docker | ||
| windows | ||
| assetcheck.sh | ||
| build.sh | ||
| ci-helper.sh | ||
| copywrite-exceptions.sh | ||
| coverage.sh | ||
| deprecations-checker.sh | ||
| dist.sh | ||
| gen_openapi.sh | ||
| go-helper.sh | ||
| semgrep_plugin_repos.sh | ||
| testciphers.sh | ||
| update_plugin_modules.sh | ||