feat: support deploying aleph-vm from a Git branch#10
Open
odesenfans wants to merge 2 commits intomainfrom
Open
feat: support deploying aleph-vm from a Git branch#10odesenfans wants to merge 2 commits intomainfrom
odesenfans wants to merge 2 commits intomainfrom
Conversation
Add the ability to deploy aleph-vm from a CI-built .deb artifact instead of a GitHub release. This uses the gh CLI to download the artifact from the latest successful workflow run for the specified branch. Configurable via manifesto.yml (branch field) or the ALEPH_VM_BRANCH environment variable. Falls back to the existing release-based flow when no branch is set.
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
.debartifact (GitHub Actions) instead of a GitHub releasefetch_vm_deb_from_branch()function usesgh run list+gh run downloadto fetch the.deblocally, thenscps it to each CRNmanifesto.yml(branchfield) orALEPH_VM_BRANCHenv var; falls back to existing release-based flow when unsetUsage
or:
Test plan
ALEPH_VM_BRANCH=mainand verify the.debis fetched from CI and installedversionfield and verify existing release-based flow still works