Reorder pipeline stages for maximum parallelism #7077
Merged
Conversation
This file contains 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
While the `windows-service` package must be built after the Windows Launcher package, there is nothing that prevents Launcher and Supervisor packages from being built in parallel, since they are mutually independent on a Habitat dependency level. Similarly, none of the exporters depend directly on either the Launcher or the Supervisor, so they can all be built at the same time as those two packages. Now, we build the Windows Service toward the end, alongside the `core/hab-pkg-cfize` exporter, which itself has a hard dependency on `core/hab-pkg-export-docker`. By reordering these and building more packages in parallel, we should be able to get through the entire pipeline in less overall time. Signed-off-by: Christopher Maier <cmaier@chef.io>
mwrock
approved these changes
Oct 22, 2019
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.
While the
windows-servicepackage must be built after the WindowsLauncher package, there is nothing that prevents Launcher and
Supervisor packages from being built in parallel, since they are
mutually independent on a Habitat dependency level.
Similarly, none of the exporters depend directly on either the
Launcher or the Supervisor, so they can all be built at the same time
as those two packages.
Now, we build the Windows Service toward the end, alongside the
core/hab-pkg-cfizeexporter, which itself has a hard dependency oncore/hab-pkg-export-docker.By reordering these and building more packages in parallel, we should
be able to get through the entire pipeline in less overall time.
Signed-off-by: Christopher Maier cmaier@chef.io