Build command runs twice unnecessarily, doubling build times about steps-xcode-test HOT 5 CLOSED

The clean option is only applied on the first build, and not on the second one. The second one should be a minimal build, as that can use the first one's intermediate files.

Do you have data about how much it would improve the performance if we'd skip the first build? In our tests the difference wasn't really significant. The double build solved an issue with a previous xcode version, as well as it reduces the log output, as the first build's output is only presented if it fails.

from steps-xcode-test.

Most projects use a different Build Config in their scheme for build than they do for test. So the first xcodebuild intermediate files aren't even used because it has to compile all over again. Right now Bitrise hangs on the first build step for ~400 seconds (with no output), than spends another ~400 seconds to make the build again for testing.

Would it be possible to just do it all in one?

xcodebuild "-workspace" "..." "-scheme" "..." "clean" "build" "test" "-destination" "platform=iOS Simulator,name=iPhone 6s,OS=latest"

from steps-xcode-test.

that's a good call, we'll add an option to use the mode you want to, e.g. if the double build solves an Xcode issue.

We'll most likely set the default to single build, to help speed up things.

Thank you for the request!

from steps-xcode-test.

New version 1.13.6 got a new input single_build.

If single_build: true, then step calls only xcodebuild OPTIONS build test OPTIONS, otherwise step runs xcodebuild OPTIONS build OPTIONS befor the test.

from steps-xcode-test.

1.13.6 is published into the StepLib - thanks again @andrewtheis for the suggestion!

from steps-xcode-test.