When setting up CI/CD workflows for Unity projects, one question that often arises is: where should we place the Unity License Server?
In most cases, the license server doesn’t need to be running all the time, especially if it’s only needed during the build process. Here’s a simple approach: deploy the license server dynamically as part of your CI job and shut it down once the build is complete. This minimizes resource usage and ensures the license server is active only when needed.
However, there are factors to consider, such as licensing agreements with Unity and security concerns. You could also consider deploying the license server within a Docker container or using cloud providers for temporary deployments during CI builds.
In this blog post, we’ll discuss these considerations further and provide insights to help you make the right decision for your CI/CD setup.
What is your suggestion? Share your thoughts and experiences with us in the comments below!