The self-hosted runner is 0.1.1: the 0.1.0 release still packs artifacts with tar, which on Windows read a drive letter as a remote host and failed the desktop release's Windows job after the installer was built; runners update themselves to this release, which packs artifacts as ZIP in the runner itself.#1
How this runs on g1t · 8 notes
- binaries: `actions/checkout` checks out from g1t.
- binaries: `actions/cache`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.
- binaries: `actions/upload-artifact`: g1t keeps artifacts with the run for 14 days, up to 60 MB each.
- binaries: `environment`: the job gets the values its secrets and variables give this environment once the environment's protection rules (required reviewers, a wait timer, which branches may deploy) let it through. Unless it says `deployment: false`, the run records a deployment to it.
- image: `actions/checkout` checks out from g1t.
- image: `actions/download-artifact`: g1t keeps artifacts with the run for 14 days, up to 60 MB each.
- image: `self-hosted`: the job runs on one of the workspace's self-hosted runners that has every label in its `runs-on`, and waits until one does.
- image: `environment`: the job gets the values its secrets and variables give this environment once the environment's protection rules (required reviewers, a wait timer, which branches may deploy) let it through. Unless it says `deployment: false`, the run records a deployment to it.
Triggered via push
syntaqx9df0e57runner-v0.1.1
Status
Failed
Total duration
14s
Artifacts
—