Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Optimize dependency resolution code path and introduce experiment to limit parallelism #140

Conversation

arunkumar9t2
Copy link
Contributor

Various improvements to optimize the dependency resolution process which remains on the critical path:

  • Ensure dependency resolution for unselected variants are skipped, only variants that pass the variant filter configured by the user will go through resolution as part of the migration.
  • Ensure Variant's extendsFrom property are correctly set for Android tests and unit test variants
  • Introduce an experiments extension property that adds limitDependencyResolutionParallelism flag which can be used to limit the no of parallel dependency resolution happening by establishing inter task dependencies that mirror the project graph. This basically ensure successors in a graph are resolved first before trying to resolve the predecessor nodes.
  • Updated tests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants