3 ms·
> https://game.ci 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 corr
by doctorpangloss 3y ago
> https://game.ci 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.
- GabeIsko 3y agoI'm having a good experience with some automation build automation with Councourse CI. Of course, I self host, and I am doing some real trivial stuff right now.
- appplication 3y ago> 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. Are you making this statement about game devs, or more broadly? I don’t know much about game dev, but if more broadly that’s a pretty spicy take.
- doctorpangloss 3y agoOnly in my experience, automated building of the client side of a game is usually low ROI. In broader contexts yeah you should be doing CI/CD.