Skip to content
This repository has been archived by the owner on Jun 28, 2024. It is now read-only.

ci: Add integration test for the confidential-containers changes scenarios #4628

Open
stevenhorsman opened this issue Mar 25, 2022 · 0 comments
Open

ci: Add integration test for the confidential-containers changes scenarios #4628

stevenhorsman opened this issue Mar 25, 2022 · 0 comments
Labels
area/confidential-containers enhancement Improvement to an existing feature needs-review Needs to be assessed by the team.

Comments

@stevenhorsman
Copy link
Member

stevenhorsman commented Mar 25, 2022 •
edited
Loading

After #4627 and kata-containers/kata-containers#3996 are complete we should have the CI/CD jobs set-up to run against the CC parameter (just regression testing and using the containerd fork until the runtime changes are merged) and all of the development changes from the CCv0 branch into main. At this point we should be able to start adding in our confidential-containers integration tests, wherever we are up to based on the plan into main and they should run.

See #4441 for some overall discussion of the merge
@stevenhorsman stevenhorsman added enhancement Improvement to an existing feature needs-review Needs to be assessed by the team. area/confidential-containers labels Mar 25, 2022
@stevenhorsman stevenhorsman mentioned this issue Mar 25, 2022
Open
@stevenhorsman stevenhorsman changed the title runtime: Add support for the confidential-containers changes ci: Add integration test for the confidential-containers changes scenarios Mar 30, 2022
@wainersm wainersm assigned wainersm and unassigned wainersm Mar 30, 2022
@stevenhorsman stevenhorsman mentioned this issue Apr 5, 2022
Closed
@wainersm wainersm mentioned this issue Apr 14, 2022
Merged
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
area/confidential-containers enhancement Improvement to an existing feature needs-review Needs to be assessed by the team.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@wainersm @stevenhorsman