search

oras-project / oras

OCI registry client - managing content like artifacts, images, packages
https://oras.land
Apache License 2.0
1.45k stars 175 forks source link

Standardize test data setup for E2E tests #710

Open qweeah opened 1 year ago

qweeah commented 1 year ago

For now, command suites require pre-baked storage image in distribution storage layout. Once https://github.com/oras-project/oras/issues/378 finishes, mount files can be changed to OCI layout so the preparation process can be done via oras copy

See original discussion:

Looks like there is very docker-specific env setup. Should probably standardize on that also.

The env setup now is based on mount files in distribution storage layout. ZOT storage is designed based on OCI layout so it's not compatible. We will definitely standardize the setup process when ORAS support OCI layout target.

Originally posted by @qweeah in https://github.com/oras-project/oras/issues/709#issuecomment-1334723703

github-actions[bot] commented 1 year ago

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days.

qweeah commented 1 year ago

This is a critical testing issue if we want to move to OCI image and distribution spec 1.1.0 and tested based on ZOT.

TerryHowe commented 1 year ago

What tasks are left to complete this?

qweeah commented 1 year ago

What tasks are left to complete this?

$REPO/test/e2e/scripts/prepare.sh has already provide a way to initalize ZOT. If users want to runt e2e against their own OCI registry, they need to write another script to copy from the OCI layouts under $REPO/test/e2e/testdata/zot. (Well, if oras have https://github.com/oras-project/oras/issues/730 completed the script is super easy to write :))

Putting this to future as the majority of the work is done.