test/api.sh: fix generation of predictable TEST_ID in GitLab CI
The `test/cases/api.sh` script relied on environment variables specific to Jenkins for detecting it if is running in a CI environment. If this was the case, it used other environment variables to construct a predictable `TEST_ID` which could be used for names of resources created in cloud-provider environment as part of the test. This is important to ensure that `cloud-cleaner` can "guess" resource names and delete them in case the test script fails to clean up after itself. With the move from Jenkins to GitLab CI, this stopped to work and the script started to generate random `TEST_ID`, which can not be guessed by the `cloud-cleaner` tool. Modify the `test/cases/api.sh` to detect the CI environment using the `CI` environment variable, which is always predefined in the GitLab CI environment [1]. [1] https://docs.gitlab.com/ee/ci/variables/predefined_variables.html Signed-off-by: Tomas Hozza <thozza@redhat.com>
This commit is contained in:
parent
a9ecf5a839
commit
1fd151ce28
1 changed files with 5 additions and 5 deletions
|
|
@ -318,12 +318,12 @@ ARCH=$(uname -m)
|
|||
SSH_USER=
|
||||
|
||||
# Generate a string, which can be used as a predictable resource name,
|
||||
# especially when running the test in Jenkins where we may need to clean up
|
||||
# especially when running the test in CI where we may need to clean up
|
||||
# resources in case the test unexpectedly fails or is canceled
|
||||
JENKINS_HOME="${JENKINS_HOME:-}"
|
||||
if [[ -n "$JENKINS_HOME" ]]; then
|
||||
# in Jenkins, imitate GenerateCIArtifactName() from internal/test/helpers.go
|
||||
TEST_ID="$DISTRO_CODE-$ARCH-$BRANCH_NAME-$BUILD_ID"
|
||||
CI="${CI:-false}"
|
||||
if [[ "$CI" == true ]]; then
|
||||
# in CI, imitate GenerateCIArtifactName() from internal/test/helpers.go
|
||||
TEST_ID="$DISTRO_CODE-$ARCH-$CI_COMMIT_BRANCH-$CI_BUILD_ID"
|
||||
else
|
||||
# if not running in Jenkins, generate ID not relying on specific env variables
|
||||
TEST_ID=$(uuidgen);
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue