From 265dda28bb0c90d08f2cf624348964195d716caa Mon Sep 17 00:00:00 2001 From: David Finol Date: Tue, 14 May 2024 23:33:30 -0500 Subject: [PATCH 1/3] Update steam.mdx Set build step id to `buildStep` to help readers avoid confusion. --- docs/03-github/06-deployment/steam.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/03-github/06-deployment/steam.mdx b/docs/03-github/06-deployment/steam.mdx index 7e82cb07..14bb2613 100644 --- a/docs/03-github/06-deployment/steam.mdx +++ b/docs/03-github/06-deployment/steam.mdx @@ -25,7 +25,7 @@ jobs: - StandaloneWindows64 # Build a Windows 64-bit standalone. - StandaloneLinux64 # Build a Linux 64-bit standalone. outputs: - buildVersion: ${{ steps.build.outputs.buildVersion }} + buildVersion: ${{ steps.buildStep.outputs.buildVersion }} steps: - uses: actions/checkout@v4 with: @@ -41,7 +41,7 @@ jobs: Library-${{ matrix.targetPlatform }}- Library- - uses: game-ci/unity-builder@v4 - id: build + id: buildStep env: UNITY_LICENSE: ${{ secrets.UNITY_LICENSE }} with: From 030a1460ed18df832bbee9a587d99b4e0c658c43 Mon Sep 17 00:00:00 2001 From: David Finol Date: Sat, 22 Nov 2025 11:53:25 -0600 Subject: [PATCH 2/3] Update troubleshooting section for disk space issues Clarified disk space issues when running multiple jobs sequentially in GitHub Actions workflows. Updated recommendations for using GitHub-hosted larger runners and self-hosted/cloud runners. --- docs/09-troubleshooting/common-issues.mdx | 14 +++++++++++--- 1 file changed, 11 insertions(+), 3 deletions(-) diff --git a/docs/09-troubleshooting/common-issues.mdx b/docs/09-troubleshooting/common-issues.mdx index 8317d6b3..80f27f27 100644 --- a/docs/09-troubleshooting/common-issues.mdx +++ b/docs/09-troubleshooting/common-issues.mdx @@ -254,8 +254,11 @@ docker: failed to register layer: write /opt/unity/Editor/Data/Resources/Package #### Explanation -When executing multiple jobs sequentially in the same workflow, there can be potential disk space -issues. For instance, if your workflow first executes tests on one docker image, such as +The default GitHub-hosted runners do not have much disk space, and Unity images and projects are often +too large to fit on the default GitHub-hosted runners. + +Furthermore, when executing multiple jobs sequentially in the same workflow, there can be potential disk +space issues. For instance, if your workflow first executes tests on one docker image, such as `unityci/editor:ubuntu-2022.3.4f1-linux-il2cpp-2`, and subsequently runs a build on another target platform, e.g., `unityci/editor:ubuntu-2022.3.4f1-windows-mono-2`, it might run out of space during the build phase. @@ -276,7 +279,12 @@ collectively consume a significant amount of disk space. at the start of your workflow to clear some space on the GitHub-hosted runner. This action can be especially useful if only a small amount of additional space is needed. -3. **Use Self-Hosted or Cloud Runners**: If your project inherently requires more disk space than +3. **GitHub-Hosted Larger Runners**: If you have a paid GitHub Enterprise Cloud or GitHub Team plan, + you can have your enterprise or organization configure + [GitHub-Hosted Larger Runners](https://docs.github.com/en/actions/how-tos/manage-runners/larger-runners) + as appropriate for your project. + +4. **Use Self-Hosted or Cloud Runners**: If your project inherently requires more disk space than what GitHub-hosted runners provide, consider switching to [Self-hosted Runners](https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners/about-self-hosted-runners) or From d3b2e642eb60f01071f1866130e823e1b9a05e89 Mon Sep 17 00:00:00 2001 From: David Finol Date: Sat, 22 Nov 2025 12:02:22 -0600 Subject: [PATCH 3/3] Run prettier --- docs/09-troubleshooting/common-issues.mdx | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/09-troubleshooting/common-issues.mdx b/docs/09-troubleshooting/common-issues.mdx index 80f27f27..2a9aa854 100644 --- a/docs/09-troubleshooting/common-issues.mdx +++ b/docs/09-troubleshooting/common-issues.mdx @@ -254,11 +254,11 @@ docker: failed to register layer: write /opt/unity/Editor/Data/Resources/Package #### Explanation -The default GitHub-hosted runners do not have much disk space, and Unity images and projects are often -too large to fit on the default GitHub-hosted runners. +The default GitHub-hosted runners do not have much disk space, and Unity images and projects are +often too large to fit on the default GitHub-hosted runners. -Furthermore, when executing multiple jobs sequentially in the same workflow, there can be potential disk -space issues. For instance, if your workflow first executes tests on one docker image, such as +Furthermore, when executing multiple jobs sequentially in the same workflow, there can be potential +disk space issues. For instance, if your workflow first executes tests on one docker image, such as `unityci/editor:ubuntu-2022.3.4f1-linux-il2cpp-2`, and subsequently runs a build on another target platform, e.g., `unityci/editor:ubuntu-2022.3.4f1-windows-mono-2`, it might run out of space during the build phase. @@ -280,9 +280,9 @@ collectively consume a significant amount of disk space. especially useful if only a small amount of additional space is needed. 3. **GitHub-Hosted Larger Runners**: If you have a paid GitHub Enterprise Cloud or GitHub Team plan, - you can have your enterprise or organization configure + you can have your enterprise or organization configure [GitHub-Hosted Larger Runners](https://docs.github.com/en/actions/how-tos/manage-runners/larger-runners) - as appropriate for your project. + as appropriate for your project. 4. **Use Self-Hosted or Cloud Runners**: If your project inherently requires more disk space than what GitHub-hosted runners provide, consider switching to