Portable Container Testing

Portable Container Testing (in dev.external) is a scenario designed to validate the JVM feature portability and consistency of Docker containers across different environments. The process involves creating a lightweight Docker container, running tests, pushing it to a Docker registry, then pulling and running it on machines with either the same or different OS/micro-architectures and running tests again. This ensures the container with JVM feature (i.e., CRIU, portable SCC, etc) behaves reliably across micro-architectures.

Currently, we have Portable Container Testing created for CRIU. For details, see https://github.com/adoptium/aqa-tests/blob/0c8ffc787bcf7f47fe3d72ebc9b10c72676f6913/buildenv/jenkins/openjdk_tests#L165-L266

For portable SCC, we will be testing with different OS and micro-architecture combinations than those used for CRIU. Initially, the portable SCC test scenarios will be added directly to the code. To support future enhancements and additional combinations, we will introduce a config folder to store imageUploadMap and imagePullMap JSON files for each feature. Adding support for a new feature will only require implementing the relevant tests and including the corresponding mapping files in the config folder.

related: automation/issues/294