Replies: 2 comments
-
No answer after 20d? |
Beta Was this translation helpful? Give feedback.
0 replies
-
Hi @jongarate You're right, this command runs every time, because it will run anyways even without it (internally), which will cause a timeout if it takes longer than expected. The command with The good thing is, you can set the path for your dependencies (resolved on step 1), so this command will be much faster. Does it work for you? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
As of fastlane version 2.156.0, I'm trying to separate the build process in the CI into the following lanes:
The idea being that (1) should take care of fetching and arranging all dependencies, currently both SwiftPM and CocoaPods, while (2) and (3) relate to ONLY building and testing respectively (e.g. NO network activity and ideally no dependency compiling).
Thing is, whenever (2) or (3) are fired fastlane underlyingly seems to execute the following:
$ xcodebuild -resolvePackageDependencies -workspace...
I'm wondering wether it would be possible to disable the
-resolvePackageDependencies
flag and, for instance, use-disableAutomaticPackageResolution
in it's place to avoid fetching SwiftPM dependencies in every lane. I've been checking the official docs and haven't found anything related. Checking fastlane source code suggests this parameter is enforced whenever we are running XCode => 11. Also tried adding an additionalxcargs
parameter to bothbuild_ios_app
andscan
to no avail.Bonus Question
For (1) I'm currently firing the following command in the respective lane:
Is the spm action a better fit for this task? I've found documentation to be scarce at best.
Beta Was this translation helpful? Give feedback.
All reactions