why is `bundle exec fastlane test` building code twice?

[tomholub]

hi @sosnovsky @ivan-ushakov please suggest if possible to improve performance of the build. Right now we have step with 2 fastlanes (do_everything and build_e2e). Maybe it's possible to cmbine them or use some option so on second building it will be faster?

Originally posted by @fcvakintos in #719 (comment)

[sosnovsky]

Why do we need 2 different builds? First is used for unit tests and second is moved to Appium dir for UI tests, right?
Maybe we can use only 1 build here - run unit tests and then move it to Appium dir?

[tomholub]

I would hope so. I'm trying that now, but I'm not well versed with this tooling. If I can't manage, you could have a look later next week. 👍

[tomholub]

Also more generally - is it really necessary to rebuild all dependencies on each build? Does the package dependency tool offer any way where we can download already prebuilt libraries? It seems most time is spent building libraries, over and over.

[tomholub]

Running a single step works but interestingly it doesn't save that much time.

Original 23 min + 16 min = 39 min

New 30 min:

Better than nothing, but maybe we'd save more time by running them in parallel on different machines after all. I'll test that later.

There is something weird about the way the scan command runs. It is configured to skip building, and yet it spends a lot of time compiling things, too. Seems like something to optimize.

[tomholub]

relevant #762

[tomholub]

I'll leave them running on separate machines for now, so the overall build times are reduced.

Later I'll ask you to look into why bundle exec fastlane test is taking so long - it seems to be building some of the code two times. One time on build, and one time on scan which have skip_build: true on them, which is surprising.

But for now I'll have you work on the issues that are already assigned to you. Thanks!

[tomholub]

maybe it's building different bundle ids - that would explain it