podman/contrib/cirrus/rootless_test.sh
Ed Santiago a47bb4d29f cirrus: minor cleanup and refactoring
...with the goal of (very soon) reusing this code, in #2947,
to run system tests in CI. This is the cleanest way I can
think of to do so without duplication or a large maintenance
burden.

Changes are:
 - replace references to 'ginkgo' with 'integration'. That
   target is already in Makefile, and is not only more
   readable, it's also more abstract. There is no reason
   for this level of code to know about ginkgo.
 - allow rootless_test.sh to accept an argument,
   that being the name of the test suite to run
   (default: integration). #2947 will enable 'system'.
 - allow integration_test.sh to serve multiple purposes,
   by checking its filename. #2947 will add a symlink,
   system_test.sh, which will then cascade down to
   invoke system tests.

Signed-off-by: Ed Santiago <santiago@redhat.com>
2019-06-03 05:34:31 -06:00

47 lines
824 B
Bash
Executable file

#!/bin/bash
set -e
remote=0
# The TEST_REMOTE_CLIENT environment variable decides whether
# to test varlinke
if [[ "$TEST_REMOTE_CLIENT" == "true" ]]; then
remote=1
fi
source $(dirname $0)/lib.sh
if [[ "$UID" == "0" ]]
then
echo "Error: Expected to be running as a regular user"
exit 1
fi
# Which set of tests to run; possible alternative is "system"
TESTSUITE=integration
if [[ -n "$*" ]]; then
TESTSUITE="$1"
fi
# Ensure environment setup correctly
req_env_var GOSRC ROOTLESS_USER
echo "."
echo "Hello, my name is $USER and I live in $PWD can I be your friend?"
echo "."
export PODMAN_VARLINK_ADDRESS=unix:/tmp/podman-$(id -u)
show_env_vars
set -x
cd "$GOSRC"
make
make varlink_generate
make test-binaries
if [ $remote -eq 0 ]; then
make local${TESTSUITE}
else
make remote${TESTSUITE}
fi