jprdonnelly/docs
1
0
Fork 0
mirror of synced 2025-12-23 11:54:18 -05:00
Code Issues Projects Releases Wiki Activity

Merge branch 'main' into patch-11

Browse Source
This commit is contained in:
Janice
2020-10-09 16:25:14 -07:00
committed by GitHub
parent cabeaf45cf 25351e513f
commit a0ce9f5d4d
165 changed files with 2254 additions and 1606 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
content/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md
View File

@@ -69,7 +69,7 @@ You can populate the runner tool cache by running a {% data variables.product.pr
path: ${{runner.tool_cache}}/tool_cache.tar.gz
```
{% endraw %}
1. Download the tool cache artifact from the workflow run. For instructions on downloading artifacts, see "[Persisting workflow data using artifacts](/actions/configuring-and-managing-workflows/persisting-workflow-data-using-artifacts#downloading-and-deleting-artifacts-after-a-workflow-run-is-complete)."
1. Download the tool cache artifact from the workflow run. For instructions on downloading artifacts, see "[Downloading workflow artifacts](/actions/managing-workflow-runs/downloading-workflow-artifacts)."
1. Transfer the tool cache artifact to your self hosted runner and extract it to the local tool cache directory. The default tool cache directory is `RUNNER_DIR/_work/_tool`. If the runner hasn't processed any jobs yet, you might need to create the `_work/_tool` directories.
After extracting the tool cache artifact uploaded in the above example, you should have a directory structure on your self-hosted runner that is similar to the following example: