The desktop release's Windows job brings its own Rust when the runner's account has none, so a runner installed as a Windows service builds it without anyone touching the machine; and the runner release builds Linux and Windows only for now, since zig cannot link the macOS targets without Apple's SDK.#3
How this runs on g1t · 22 notes
- linux: `timeout-minutes: 90`: a job on g1t's own machines is stopped at 60 minutes. A self-hosted runner runs it for as long as it asks, up to 24 hours.
- windows_cross: `timeout-minutes: 90`: a job on g1t's own machines is stopped at 60 minutes. A self-hosted runner runs it for as long as it asks, up to 24 hours.
- version: `actions/checkout` checks out from g1t.
- linux: `actions/checkout` checks out from g1t.
- linux: `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.
- linux: `actions/upload-artifact`: g1t keeps artifacts with the run for 14 days unless the repository says otherwise, up to 5 GiB each.
- linux: `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.
- windows: `actions/checkout` checks out from g1t.
- windows: `actions/upload-artifact`: g1t keeps artifacts with the run for 14 days unless the repository says otherwise, up to 5 GiB each.
- windows: `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.
- windows: `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.
- windows_cross: `actions/checkout` checks out from g1t.
- windows_cross: `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.
- windows_cross: `actions/upload-artifact`: g1t keeps artifacts with the run for 14 days unless the repository says otherwise, up to 5 GiB each.
- windows_cross: `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.
- macos: `actions/checkout` checks out from g1t.
- macos: `actions/upload-artifact`: g1t keeps artifacts with the run for 14 days unless the repository says otherwise, up to 5 GiB each.
- macos: `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.
- macos: `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.
- publish: `actions/checkout` checks out from g1t.
- publish: `actions/download-artifact`: g1t keeps artifacts with the run for 14 days unless the repository says otherwise, up to 5 GiB each.
- publish: `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.