FrooxEngine, Resonite & CI/CD

Today, we’re going to have a look at the CI/CD pipelines for Resonite, and admittedly, I’m at my third attempt at writing this blog post. I started writing this post back when work started on the pipelines, trying to keep it in sync. However, while I was adding more features, and patching others, I didn’t have the time to update the draft which ended up completely desynchronized from the pipelines themselves. The release of the Unity renderer as an Open-Source project also changed plans quite a bit, as the original post was written while the project was still internal. Now that I finally found some time, and energy, to write it, let’s do a quick dive into Resonite and the pipelines powering it. The anatomy of a pipeline This paragraph is for those who have no idea what CI/CD is. To keep it short, CI/CD is the practice of automating testing and builds when a change is made (or pushed) to a project’s code. Those workflows can even be used to publish a new version of the software, which…