From 848037863966aca9c1a8c4ba6afbbd37cd4096c7 Mon Sep 17 00:00:00 2001 From: Pavel Sturc Date: Wed, 3 Jan 2024 15:05:36 +0100 Subject: [PATCH] docs: add note about test-images quay repo --- docs/Installation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/Installation.md b/docs/Installation.md index a12b5f0d5..05e9e45f6 100644 --- a/docs/Installation.md +++ b/docs/Installation.md @@ -91,7 +91,7 @@ are in the [infra-deployments](https://github.com/redhat-appstudio/infra-deploym Most of the tests could require you to have specific container image repo's created (if you're using your own container image org/user account (`QUAY_E2E_ORGANIZATION`) or your own GitHub organization (`MY_GITHUB_ORG`). In that case, before you run the test, make sure you have created -* `test-images` repo in quay.io, i.e. `quay.io//test-images` and make it **public** +* `test-images` repo in quay.io, i.e. `quay.io//test-images` and make it **public** (this repo will be used for pushing container images produced by tests) * also make sure that the docker config, that is encoded in the value of `QUAY_TOKEN` environment variable, contains a correct credentials required to push to `test-images` repo. And make sure the robot account or user account has the **write** permissions set for `test-images` repo which is required by the tests to push the generated artifacts. * fork following GitHub repositories to your org (specified in `MY_GITHUB_ORG` env var) * https://github.com/redhat-appstudio-qe/devfile-sample-hello-world (for running build-service tests)