Others created custom tools which would trigger Katana builds and download them to the CI machines.Īll the solutions were quite hacky and not particularly generic. Some of them ended up running CI on physical machines that would just have the editor permanently installed on them with hard-coded paths to each version needed.

So last year we ended up with a lot of the package repos having their own custom way of grabbing the editor. We have had no seamless and unified way for the package CI to request a specific Editor build.

Packages have their own repositories with a new CI system running on them.įor a package’s CI to be successful, the most important thing is its main dependency: the Unity Editor. We, of course, wanted to be able to verify and publish these packages and make sure that each of them would play nicely with the different editor versions, and satisfy our internal quality requirements. It was also a much-needed step on our roadmap to DOTS.īut like any transition, this new technical paradigm came with a set of challenges. This has allowed us to speed up the delivery process and help take some Unity features and extensions to the next level. More and more of Unity features are being moved from the main Unity repository and stored into separate packages repositories. Then, we decided to evolve and start using packages.

Unity editor download