measure fastlane startup time via execution time of --help
command 🏎️
#13166
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Checklist
bundle exec rspec
from the root directory to see all new and existing tests passbundle exec rubocop -a
to ensure the code style is validMotivation and Context
Fastlane can be pretty slow to start. Slow startup is bad.
Description
This PR adds a new lane
benchmark_help_command
that is also run duringexecute_tests
. It installs a (cross platform) node tool via npm calledgnomon
that prepends timestamps to lines of out and measures the total execution time. This total is extracted and output in the lane. To make sure we get a good overview, the lane runsfastlane --help
3 times and outputs it runtime.In the future this lane can be used to benchmark
fastlane
and that way track and measure the effect of any changes (like #13167).