You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The added machine table links the machine's assigned labels to the jobs required labels.
Corrected some mistakes and label assignments.
Formatting.
Fixes: confidential-containers#316
Signed-Off-By: Ryan Savino <ryan.savino@amd.com>
Copy file name to clipboardexpand all lines: docs/DEVELOPMENT.md
+23-11
Original file line number
Diff line number
Diff line change
@@ -92,22 +92,34 @@ In order to be merged your opened pull request (PR) should pass the static analy
92
92
93
93
The e2e tests jobs are executed on a variety of CcRuntime, configurations and platforms. These jobs that require confidential hardware (Intel TDX, AMD SEV, IBM SE, etc...) run on bare-metal machines and are often referred as "TEE tests". The remaining tests (a.k.a "Non-TEE") are executed on Virtual Machines (VM) deployed on-demand.
94
94
95
+
This is a list of the bare-metal machines and VMs that are utilized by the project for CI testing:
96
+
97
+
| Machine | Type | TEE Capability | Assigned Labels |
The required labels specified for a job will determine what machine it lands on by matching the machine's assigned labels.
111
123
112
124
Some of the e2e jobs are not triggered automatically. We recommend to trigger them only after some rounds of reviews to avoid wasting resources. They can be triggered only by writing `/test` in PR's comment.
0 commit comments