podman/test/e2e/build
Ashley Cui 9ce3c0a87a Move secret-verify-leak containerfile into its own Directory
Secret-verify-leak is causing flakes, when running in parallel tests.
This is because remote secrets are copied into the context directory to
send to the API server, and secret-verify-leak is doing a COPY * and
then checking if the temporary secret file ends up in the container or
not. Since all the temporary files are prefixed with
"podman-build-secret", this test checks if podman-build-secret is in the
image. However, when run in parallel with other tests, other temporary
podman-build-secrets might be in the context dir. Moving
secret-verify-leak into its own directory makes sure that the context
dir is used only by this one test.

Also renamed Dockerfile -> Containerfile and cleaned up unused
Containerfiles.

Signed-off-by: Ashley Cui <acui@redhat.com>
2022-03-08 10:05:42 -05:00
..
basicalpine Fix podman build --pull-never 2021-03-27 05:33:30 -04:00
envwithtab inspect: printTmpl must Flush writer 2021-09-09 16:37:24 +05:30
secret-verify-leak Move secret-verify-leak containerfile into its own Directory 2022-03-08 10:05:42 -05:00
squash Fix podman build --pull-never 2021-03-27 05:33:30 -04:00
workdir-symlink container: workdir resolution must consider symlink if explicitly configured 2022-03-02 19:02:33 +05:30
Containerfile.with-multiple-secret Move secret-verify-leak containerfile into its own Directory 2022-03-08 10:05:42 -05:00
Containerfile.with-secret Move secret-verify-leak containerfile into its own Directory 2022-03-08 10:05:42 -05:00
anothersecret.txt podman-remote: copy secret to contextdir is absolute path on host 2021-11-30 14:19:29 +05:30
context_dir_a_file Add new test suite for build 2019-11-16 19:19:49 -05:00
secret.txt podman-remote: copy secret to contextdir is absolute path on host 2021-11-30 14:19:29 +05:30