ci: parallelize CRN install with CCN stack + contract deploy#13
Open
odesenfans wants to merge 1 commit intomainfrom
Open
ci: parallelize CRN install with CCN stack + contract deploy#13odesenfans wants to merge 1 commit intomainfrom
odesenfans wants to merge 1 commit intomainfrom
Conversation
Splits the sequential "Start stack → Deploy contracts → Install and register CRN" block into a parallel phase (CCN up + deploy contracts || CRN --install) followed by a serial --register step. CRN state setup is moved to its own fast prep step so both branches have what they need. Both sides' logs are captured and printed after wait so failures remain easy to diagnose. Expected saving: 2-3 min off the ~15 min PR pipeline.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
--installwith CCN--up+--deploy-contractsin the PR integration-tests workflow. Both branches' logs are captured and printed afterwaitso failures stay easy to read.--registerstays serial since it needs the CCN aggregate up and accounts funded from contract deploy.Expected saving: ~2-3 min off the ~15 min pipeline — the CRN install step (~3-4 min sequentially) now overlaps with the ~3 min of CCN stack-up + contract-deploy work.
Separate follow-ups (not in this PR):
Test plan
ccn.logandcrn-install.logsections are both present in the step output.