Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

allow other manifests in l4v-deploy #357

Merged
merged 2 commits into from
Jul 19, 2024
Merged

allow other manifests in l4v-deploy #357

merged 2 commits into from
Jul 19, 2024

Conversation

lsf37
Copy link
Member

@lsf37 lsf37 commented Jul 18, 2024

Add mechanism for deploying after preprocess and after proof test to manifests other than devel.xml/default.xml. Currently only mcs-devel.xml/mcs.xml are allowed.

@lsf37 lsf37 requested a review from corlewis July 18, 2024 07:49
@lsf37 lsf37 added the verification actions related to proofs and l4v label Jul 18, 2024
@lsf37 lsf37 self-assigned this Jul 18, 2024
@lsf37 lsf37 force-pushed the l4v-deploy-update branch 2 times, most recently from 19d5710 to 091b1f6 Compare July 18, 2024 07:52
l4v-deploy/common.py Outdated Show resolved Hide resolved
lsf37 added 2 commits July 19, 2024 09:28
Add mechanism for deploying after preprocess and after proof test to
manifests other than devel.xml/default.xml. Currently only mcs.xml and
mcs-devel.xml are allowed.

Signed-off-by: Gerwin Klein <[email protected]>
@lsf37 lsf37 force-pushed the l4v-deploy-update branch from 091b1f6 to 5c4987e Compare July 18, 2024 23:28
@lsf37 lsf37 merged commit 5c4987e into master Jul 19, 2024
7 checks passed
@lsf37 lsf37 deleted the l4v-deploy-update branch July 19, 2024 04:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
verification actions related to proofs and l4v
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants