Skip to content

Commit

Permalink
For E2E upgrade test, automatically determine the channel to use (#10461
Browse files Browse the repository at this point in the history
)

* 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>
  • Loading branch information
dereknola authored Jul 11, 2024
1 parent c36db53 commit 58ab259
Showing 1 changed file with 7 additions and 1 deletion.
8 changes: 7 additions & 1 deletion .drone.yml
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down

0 comments on commit 58ab259

Please sign in to comment.