action-junit-report VS unity-actions

``` now we need to parse the report, I've been using [action-junit-report](https://github.com/mikepenz/action-junit-report) for that

In the most recent game I automated builds for the initial build took 1-3 hours, but subsequent builds with the Library/ folder cached took 5-10 minutes.

Are you switching platforms between builds locally? (like building one for web / server / pc / mac etc). Platform switching essentially blows away the cache, making it take the full build time each time. There was an asset years back that would create folders for each platform's Library/ cache and switch between them when you switched build platforms.

In CI (eg using https://game.ci) you can prefix build cache keys with the platform to manage that automatically.

Unity Cloud Build is in general slower/more flakey/sometimes has cache issues compared to DIY CI, but it should speed up after a successful first build as long as it caches the Library/ folder, and they do separate that out by build platform properly. (Worth checking each build config setting is set to cache that)

> https://game.ci

I don't recommend it.

Game CI has been in development for a long time. It only really supports GitHub Actions. It can't correctly build il2cpp Unity projects. The licenses needed to run it are more expensive than Unity Build Automation / Unity Cloud Build. If you want to automate Unity builds and you don't want to learn the Windows Containers ecosystem, Jenkins and/or Tekton, you should use Unity's service.

CI/CD is a bad choice for most developers, on most platforms, for most clients. That said, it makes sense to do for your backends.

> or (as has happened to us with different game web service/API/middleware providers) they may choose to abruptly deprecate the service upon which you built.

Which service was that? GameSparks? That sucks.

> with inappropriate cloud dev tooling

Well everyone takes their own journey to discover how shitty Lambda, Cognito, CloudFormation and related are.

> with basically any datastore other than Redis you will run in to issues matchmaking

Matchmakers do not have to be complicated.

I've been struggling with getting the docker images provided by https://game.ci/ to build his project at all, let alone automating it in a pipeline.

https://game.ci/ has fantastic GitHub actions to automate all of this on each PR or push to main etc and then just upload the result of the build as an artifact and job done - takes minutes to setup and you can use your own machine as a self hosted runner to get the same build speed as local builds

These guys did a wonderful job at providing a docker-based build environment for Unity, btw: https://game.ci/

(Someone's built something similar for Unity, but it wasn't as one click when I last looked -- especially since Unity may require licenses.)

My repositories are on github, so I'm using Github Actions for build automation - I found it really easy to setup compared to other platforms. + There's basically a ready-made action for building with unity - game.ci (although I wrote my own solution for iOS).