Support parallel building of Docker images #52920
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Mark Vieira <[email protected]>
|
Pinging @elastic/es-core-infra (:Core/Infra/Build) |
|
@elasticmachine update branch |
mark-vieira
added a commit
that referenced
this pull request
Feb 28, 2020
mark-vieira
added a commit
that referenced
this pull request
Feb 28, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
We currently build two variants of our Docker image: oss and default. Because these tasks both belong to the same Gradle subproject
:distribution:dockerthey cannot be run concurrently by default. Rather than introducing more subprojects just for the purposes of parallel build execution, this PR adds aDockerBuildTaskwhich leverages the Gradle Worker API which allows intra-project task parallelism.This should considerably help out builds that spend the majority of their time on building these images. In the example below you can see the task execution timeline is very sparse toward the end of the build due mainly to the fact that Docker image construction is done serially.