Switch to matrix strategy to parallize provider family builds #105
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.
Description of your changes
This PR implements a matrix strategy for building provider families in smaller chunks. The
Provider Publish Service Artifacts
workflow now accepts asize
parameter which specifies the maximum number of subpackages to be built in a matrix job and a newconcurrency
parameter which is passed to theup xpkg batch
command as the value of the--concurrent
option to control the maximum batch concurrency in the build pipeline.I have:
make reviewable test
to ensure this PR is ready for review.How has this code been tested
Tested in the Github workflow of
upbound/provider-aws
with the correspondingup xpkg batch
command.