scan is twice slower on building code

[fastlanebot]

Original issue by @yakimant - Imported from fastlane/scan#35

As I see - the difference between my xcodebuild arguments and scan generated is:
I run clean test and scan runs clean build test.

I also see duplicates of compiling lines.

Is it building twice?

[fastlanebot]

@tutipeti commented

Any feedback here? I find it funny how fastlane is telling me that it saved me time when I can easily see that scan is compiling twice - so running the tests takes about twice as long as it did when I were using only xcodebuild.

[fastlanebot]

@arunks commented

Looks like this is an issue. I tried running the xcodebuild command generated by scan directly without the build option. Just clean test. That seems to have cut the time in half.

[fastlanebot]

@KrauseFx commented

@yakimant did you test everything when removing the build part of the command? I'm pretty sure there was a reason this was added to scan a while back, but can't remember why.

[fastlanebot]

@attheodo commented

+1 for that. scan takes significantly more because it involves rebuilding the whole thing VS hitting CMD+U on Xcode. clean: false doesn't seem to help.

[fastlanebot]

@arunks commented

@KrauseFx I have been using xcodebuild to workaround this problem, instead of Scan. Currently, I am just passing the test command and have seen no issues with it in running our CI.

Also, I compared the execution times of just xcodebuild test from fastlane and using Scan from fastlane. Scan is considerably slower because does a build and test. Hope this helps.

I have a PR, if you think everything's alright - fastlane-old/scan#62

[fastlanebot]

@kdawgwilk commented

I am also seeing not only everything built twice but the tests are being ran twice 😁 Looks like I am going to switch back to xcodebuild till it gets fixed

[fastlanebot]

@Corristo commented

same here.

[fastlanebot]

@kdawgwilk commented

Was able to speed things up thanks to #86 by using gym to build the binary first then run scan with the new skip_build flag and then deploying same binary that was used for the tests 😊 before this change scan would build the app and test and then gym would build again after tests succeeded

[fastlanebot]

@KrauseFx commented

Yeah, thanks for updating this issue, this is now implemented with fastlane-old/scan#86

[ivanbruel]

@kdawgwilk any chance you can provide a concrete example on your work around?

My StackOverflow post provides a bit of context.

[TKBurner]

@ivanbruel Just set the --skip_build flag to true. Thanks!