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

Add AWS Nitro Enclaves test execution to the CI system #168

Closed
dreemkiller opened this issue Jul 7, 2021 · 2 comments
Closed

Add AWS Nitro Enclaves test execution to the CI system #168

dreemkiller opened this issue Jul 7, 2021 · 2 comments
Labels
enhancement New feature or request

Comments

@dreemkiller
Copy link
Member

Requested feature
Currently, the CI builds for SGX, builds for TrustZone, and runs the tests for TrustZone. We need to add build and run for AWS Nitro Enclaves.

Motivation
Unless the AWS nitro platform is being built and run in the CI system, the AWS Nitro support will atrophy and suffer from bitrot.

Additional context
We need to modify the CI system to start on an AWS-Nitro-supported system. To be clear, I'm not sure how to do this with the current CI system.

@dreemkiller dreemkiller added the enhancement New feature or request label Jul 7, 2021
@dreemkiller
Copy link
Member Author

It appears that adding AWS Nitro builds to veracruz can be done fairly easily: edit buildspec.yml to add

make nitro-veracruz-server-test-dry-run
make nitro-veracruz-test-dry-run

to the build commands.

It is likely that the docker image being used for the CI would need to be updated, though.

Actually running the Nitro tests is a different matter. This would require modifying the CodeBuild environment to be run on an EC2 instance that supports AWS Nitro Enclaves, which I'm not sure is possible.

@gbryant-arm
Copy link
Contributor

Done in #258 and superseded by #514

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants