A wrapper on top of MicroShift upstream e2e tests to be run on hosts with a running MicroShift cluster.
The container is based on deliverest, which handles the remote execution.
PWD
should not be a major directory like ${HOME}
or similar, to avoid the following error:
Error: SELinux relabeling of /home/cloud-user is not allowed
So create a custom subdir somewhere, then run everything from it. Furthermore, PWD
should contain id_rsa
(and eventually also pull-secret
; right now this is assumed to be on the target host already, just like a custom bundle).
For debug purposes (e.g. when run outside of the sanitized environment ensured by the pipeline), use --pull=always
policy for podman run
. Otherwise you might end up running an old local image instead of pulling a fresh one.
TARGET_FOLDER=ms-backend-e2e
USER=crcqe
HOST=windows-crcqe.tpb.lab.eng.brq.redhat.com
BUNDLE_PATH="C:/Users/crcqe/Downloads/crc_microshift_hyperv_4.13.6_amd64.crcbundle"
podman run --pull=always --network=host --rm -it --name microshift-backend-e2e \
-e TARGET_HOST=${HOST} \
-e TARGET_HOST_USERNAME=${USER} \
-e TARGET_HOST_KEY_PATH=/data/id_rsa \
-e TARGET_FOLDER=${TARGET_FOLDER} \
-e TARGET_RESULTS=junit/junit*.xml \
-e OUTPUT_FOLDER=/data \
-v $PWD:/data:z \
-v $PWD/pullsecret:/opt/ms-backend-e2e/pullsecret:z \
quay.io/rhqp/microshift-backend-e2e:v4.13.6-windows-amd64 \
ms-backend-e2e/run.ps1 \
-targetFolder ${TARGET_FOLDER} \
-junitResultsPath ${TARGET_FOLDER}/junit \
-pullSecretFile ${TARGET_FOLDER}/pullsecret \
-bundlePath ${BUNDLE_PATH}
TARGET_FOLDER=ms-backend-e2e
USER=crcqe
HOST=macmini-crcqe-2.tpb.lab.eng.brq.redhat.com
BUNDLE_PATH="/Users/${USER}/Downloads/crc_microshift_vfkit_4.13.6_amd64.crcbundle"
podman run --pull=always --network=host --rm -it --name microshift-backend-e2e-darwin \
-e TARGET_HOST=${HOST} \
-e TARGET_HOST_USERNAME=${USER} \
-e TARGET_HOST_KEY_PATH=/data/id_rsa \
-e TARGET_FOLDER=${TARGET_FOLDER} \
-e TARGET_RESULTS=junit/junit*.xml \
-e OUTPUT_FOLDER=/data \
-v $PWD:/data:z \
-v $PWD/pullsecret:/opt/ms-backend-e2e/pullsecret:z \
quay.io/rhqp/microshift-backend-e2e:v4.13.6-darwin-amd64 \
ms-backend-e2e/run.sh \
-t ${TARGET_FOLDER} \
-p ${TARGET_FOLDER}/pullsecret \
-r ${TARGET_FOLDER}/junit \
-b ${BUNDLE_PATH}
TARGET_FOLDER=ms-backend-e2e
USER=cloud-user
HOST=rhel-crcqe.tpb.lab.eng.brq.redhat.com
BUNDLE_PATH="/home/${USER}/Downloads/crc_microshift_libvirt_4.13.6_amd64.crcbundle"
podman run --pull=always --network=host --rm -it --name microshift-backend-e2e \
-e TARGET_HOST=${HOST} \
-e TARGET_HOST_USERNAME=${USER} \
-e TARGET_HOST_KEY_PATH=/data/id_rsa \
-e TARGET_FOLDER=${TARGET_FOLDER} \
-e TARGET_RESULTS=junit/junit*.xml \
-e OUTPUT_FOLDER=/data \
-v $PWD:/data:z \
-v $PWD/pullsecret:/opt/ms-backend-e2e/pullsecret:z \
quay.io/rhqp/microshift-backend-e2e:v4.13.6-linux-amd64 \
ms-backend-e2e/run.sh \
-t ${TARGET_FOLDER} \
-p ${TARGET_FOLDER}/pullsecret \
-r ${TARGET_FOLDER}/junit \
-b ${BUNDLE_PATH}
- Create a new branch, e.g.
v4.13.6
and add all changes needed alongside this version change. - Merge the branch into
main
. - Create a tag, e.g.
v4.13.6
and push it tomain
withgit push origin v4.13.6
. - GH-Actions will trigger a build based on the presence of the new tag and push the new image to quay.io.