steam content server to unity cloud build

Streamlining Unity Cloud Builds: The Benefits of Local Development

In our ongoing quest for efficiency and developer happiness, we've made the decision to focus on Windows-based development environments, leaving Mac builds for another time. By doing so, we've gained a significant advantage that allows us to build projects locally in the same way as our cloud-based build server. This means developers can test their work end-to-end within their local branches whenever needed.

However, there are certain tasks that don't add value during normal development cycles and can be handled at release time instead. These include copying documentation, creating installers, and making updates to our version control system (Git). Our Jenkins setup with a local Nuke build script handles the majority of our build and installer building needs.

When it's time for a public release, we have a separate release/build script that takes care of tagging commits, merging them into master, generating release notes, and handling uploads. This script runs on each commit or pull request and ensures everything works as expected by running tests and uploading builds to a QA share for manual testing.

In summary, our decision to focus on Windows-based development has allowed us to streamline our build process and make local development more efficient. By leveraging Jenkins and Nuke scripts, we can automate many of the tasks associated with building and releasing our projects, freeing up developers to focus on what matters most - creating great content for Unity Cloud Build.

Steam content server to unity cloud build