GitLab-CI-CD VS godot-ci

As with the earlier post on PHP linting within GitLab CI/CD, in a real scenario this would be split into two projects. In my real usage, I have one project with the general CI/CD functionality, then the specific website project can extend from those functions to push out to the server. In this demo scenario, it is all in one project of my GitHub.

I split this into two pieces, taking advantage of GitLab’s ability to extend other functions, even functions in other projects. My real work scenario is using GitLab, hence using GitLab CI. For the purposes of sharing here, I’ve put them in my personal GitHub. I know that’s an unintuitive combination.

I found this Github Action https://github.com/abarichello/godot-ci ( please let me know if there are any official / "better" alternatives ? ) and started with the following

This little project is based on the Barichello CI/CD project for Godot 3.X

Unfortunately, it does not support Godot 4 (unless you know something I don't): https://github.com/abarichello/godot-ci/issues/98

aBARICHELLO/godot-ci

I’ve had success starting with this as a baseline.

It's amazing! However it broke with Godot 3.4 Android and OSX exports so I had to write a custom Dockerfile and push it do Dockerhub to update my template to 3.4. I also shared this and reported on their issue page. You can find more details here: https://github.com/abarichello/godot-ci/issues/62

I'll try creating a repository for reference where I'll add an action to export at each new tag (but you can already find examples for that on godot-ci). This post might become a tutorial somewhere.