Add support for building private dependencies in CI #6728
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.
PR Description: Add Support for Building Private Dependencies in CI
This PR introduces changes to support building private dependencies in the CI pipeline, specifically for private Cadence repositories.
Key Changes
Update CI steps to load Cadence Deploy Key in CI:
CADENCE_DEPLOY_KEY
into the SSH agent for accessing private repositories.SSH_AUTH_SOCK
in the environment.CADENCE_DEPLOY_KEY
is not set, allowing the workflow to continue.Update
GOPRIVATE
Configuration:GOPRIVATE
togithub.com/onflow/*
in both the GitHub Actions workflow and theMakefile
to bypass the Go module proxy for private repositories.Impact
These changes enable seamless fetching and building of private Cadence dependencies during CI, improving the reliability and security of the build process.