Hi there,
We are looking to use Unity Cloud Build (DevOps Build Automation) as our build platform, however we have ran into an issue.
In order to improve repo size and developer workflow, we use embedded packages for our common libraries/packages of work. As part of this process, each package may contain a .unitypackage containing essential resources for that package that cannot be stored otherwise (prefabs/meshes/textures/etc).
So our process is that we have an editor script that, upon opening the project, will cycle through each embedded package and will import those .unitypackages so the developer has complete access to the assets within which will often be references in scenes/scripts.
The issue we are experiencing with Unity’s DevOps Build Automation is that requirement for those .unitypackages to be imported before builds occur.
We are trying to make use of the “Pre-Export Method” option within the Configuration settings of a DevOps Build Automation to import these packages before the build attempt, however the method itself is not a blocking method. Therefore it will still attempt to build the project before the packages have been imported and will build scenes (that are reliant on some of those assets) in a broken form.
Is it possible to have the build-step blocked until this import process is complete? If so, how? Otherwise would you have any other suggestion to allow us to use Unity’s Cloud Build Automation.