You will need to do the following before we start: That looks way better, doesn't it? ) Setting everything up So as a first step, we decided to reduce the manual steps to the following when there's a successful build. Not only is the list above extremely time consuming, but almost every step is error prone to all kinds of mistakes because there are so many manual steps. Repeat steps 4-8 for every platform you would like to update.Ī philosophy that we strongly hold at Lavapotion is to reduce all the "screw-up-able" steps that can occur in our process and automate as much as possible.Decide if they should get an email notification.Choose the Distribution Groups that should have access to this specific build.Choose the app that's on the platform you want to update.Download all the successful builds for the platforms you want to upload to HockeyApp to your computer.To break it down into a step-by-step instruction - take a look at the list below. The obvious way to connect the services is to do it manually everytime.
You can also notify people with an email with a changelog when a new build is ready. HockeyApp got distribution groups that you can add/restrict to any builds pretty much whenever you want. Sure, you can share all your builds in Unity Cloud Build by creating a share link and send it to the people that needs it, but there's a whole manual process involved there and no easy way to restrict downloads to certain groups.
0 kommentar(er)
