-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Add Multiplex Workers support for Android builds #10773
Comments
This issue is specific about changing Android rules/workers to using multiplexing. The infrastructure changes are done, so this has nothing to do with local execution. (Nor remote execution.) |
If your Android workers are written in Java, take a look at WorkRequestHandler, a generic class to handle the request/response and multithreading parts of multiplexing. Of course, the worker itself needs to be thread-safe, including not sharing temp files between threads. |
Thank you for contributing to the Bazel repository! This issue has been marked as stale since it has not had any activity in the last 2+ years. It will be closed in the next 14 days unless any other activity occurs or one of the following labels is added: "not stale", "awaiting-bazeler". Please reach out to the triage team ( |
This issue has been automatically closed due to inactivity. If you're still interested in pursuing this, please reach out to the triage team ( |
Description of the problem / feature request:
From what I can see from https://docs.bazel.build/versions/master/multiplex-worker.html and source code is that Multiplex Workers are only supported for Scala and maybe Java. It would be nice to get this support for Android build actions as well as Android builds tend to be large and slow.
Feature requests: what underlying problem are you trying to solve with this feature?
Improve Android's build performance.
What operating system are you running Bazel on?
Linux & Mac
Have you found anything relevant by searching the web?
The text was updated successfully, but these errors were encountered: