There's now an additional Google Cloud Function handling push notifications. A build is triggered straight after the config is created, whose only purpose is to checkout the branch and do the initial import. I now ask my team to push the new branch immediately, and the Cloud Build config is created with autoBuild disabled but importantly also configured not to do a player export (which is a useful feature that I think is only available through the API). Instead of waiting for a build to test, it becomes tempting to merge straight into develop and get a build much sooner. When a further commit is pushed, the build takes a long time because there's no library cache and Unity has to import the assets. Cloud Build will miss that commit, and a build won't be triggered. Although I create the new configs with autoBuild enabled, developers on my team sometimes push a new feature branch and an initial commit (new/updated files) at the same time. A problem with the above setup has quickly emerged.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |