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

run full l4v on AWS #80

Closed
lsf37 opened this issue Jun 21, 2021 · 1 comment · Fixed by #113
Closed

run full l4v on AWS #80

lsf37 opened this issue Jun 21, 2021 · 1 comment · Fixed by #113
Assignees
Labels
verification actions related to proofs and l4v

Comments

@lsf37
Copy link
Member

lsf37 commented Jun 21, 2021

trigger a full l4v regression test build for a matrix of architecture on AWS, report results through GitHub status.

Since this costs money, it'll need some access control, either org members only for PR, or triggered by label.

@lsf37 lsf37 added the verification actions related to proofs and l4v label Jun 21, 2021
@lsf37 lsf37 added this to To Do in Bamboo replacement via automation Jun 21, 2021
@lsf37
Copy link
Member Author

lsf37 commented Jun 21, 2021

There are a bunch of options for how to trigger an AWS run. Some requirements:

  • needs access control, i.e. manual/restricted trigger shouldn't be circumventable by adding/changing code in the repo. Could be via secrets or different ways of invoking the action, or by using a webhook and doing the entire rest on AWS

  • needs ability to spin up and shut down test runners on demand

  • should have a global max number of runners to limit cost rate

  • needs a hard timeout

  • would be nice to treat separate architectures as completely separate runs for reporting (not like Bamboo currently)

  • would be nice to see intermediate log output

@lsf37 lsf37 moved this from To Do to In Implementation in Bamboo replacement Jul 8, 2021
@lsf37 lsf37 linked a pull request Jul 12, 2021 that will close this issue
@lsf37 lsf37 moved this from In Implementation to Testing/Review in Bamboo replacement Jul 13, 2021
Bamboo replacement automation moved this from Testing/Review to Done Jul 13, 2021
@lsf37 lsf37 self-assigned this Jul 30, 2021
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
No open projects
Development

Successfully merging a pull request may close this issue.

1 participant