For E2E upgrade test, automatically determine the channel to use (#10461)

* For E2E upgrade test, determine the upgrade channel Signed-off-by: Derek Nola <derek.nola@suse.com> * Fix typos Signed-off-by: Derek Nola <derek.nola@suse.com> --------- Signed-off-by: Derek Nola <derek.nola@suse.com>

For E2E upgrade test, automatically determine the channel to use (#10461)
58ab2592 · Derek Nola · GitHub · c36db53e · 58ab2592
Unverified Commit 58ab2592 authored Jul 11, 2024 by Derek Nola Committed by GitHub Jul 11, 2024
Hide whitespace changes
Inline Side-by-side

Showing with 7 additions and 1 deletion

.drone.yml .drone.yml +7 -1

No files found.
--- a/.drone.yml
+++ b/.drone.yml
@@ -639,7 +639,13 @@ steps:
    if [ "$DRONE_BUILD_EVENT" = "pull_request" ]; then
      cd ../upgradecluster
      vagrant destroy -f
-      E2E_RELEASE_CHANNEL="latest" go test -v -timeout=45m ./upgradecluster_test.go  -ci -local
+      # Convert release-1.XX branch to v1.XX channel
+      if [ "$DRONE_BRANCH" = "master" ]; then
+        UPGRADE_CHANNEL="latest"
+      else
+        UPGRADE_CHANNEL=$(echo $DRONE_BRANCH | sed 's/release-/v/')
+      fi
+      E2E_RELEASE_CHANNEL=$UPGRADE_CHANNEL go test -v -timeout=45m ./upgradecluster_test.go  -ci -local
      cp ./coverage.out /tmp/artifacts/upgrade-coverage.out
    fi
  - docker stop registry && docker rm registry