This one is for the Unity developers with projects on GitHub looking for a way to go faster.
When working on a Unity project, you may find yourself making many builds to play test your changes. Since Unity locks the editor while building, this can leave you twiddling your thumbs for what seems like hours. By automating your builds, you can get your your time back, and at the same time streamline the development process for your team.
In this guide, we walk through how to use GitHub Actions to automate Unity builds. We learn step by step how to create a GitHub workflow, add the necessary secrets, and choose an appropriate build machine.
Note: in the article, we recommend using our Buildalon runners to speed up your builds, but this is completely optional. You can use standard GitHub runners or your own self-hosted runners instead.
Thanks for reading!
1 Like
I set up build automation for GitHub with GameCI. I can only recommend it. Any issues I had was with trying to understand how the GitHub Actions system worked.
GHA is not an intuitive scripting system but rather well documented so it does require quite some time for first time users primarily because each change takes some time due to commit, push, wait for actions to run or run them manually, then wait for it to either succeed or fail.
Good to hear about your experience @CodeSmile!
We hear you on the difficulty of learning to write a GitHub actions workflow. We built a workflow generator on our site so hopefully it’s easier for folks to get started.
GameCI has some actions similar to ours, but we tried to simplify some of the process (like avoiding docker containers) and added some additional actions to deploy to app stores.
Oh, I see. I just skimmed over the article and thought it was primarily a GitHub Actions tutorial. I didn’t realize you are providing a competing offer to GameCI. I didn’t mean to dissuade. 