Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: v2 migration e2e tests #1727

Draft
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

emosbaugh
Copy link
Member

What this PR does / why we need it:

Which issue(s) this PR fixes:

Does this PR require a test?

Does this PR require a release note?


Does this PR require documentation?

Copy link

github-actions bot commented Jan 21, 2025

This PR has been released (on staging) and is available for download with a embedded-cluster-smoke-test-staging-app license ID.

Online Installer:

curl "https://staging.replicated.app/embedded/embedded-cluster-smoke-test-staging-app/ci/appver-dev-63330aa" -H "Authorization: $EC_SMOKE_TEST_LICENSE_ID" -o embedded-cluster-smoke-test-staging-app-ci.tgz

Airgap Installer (may take a few minutes before the airgap bundle is built):

curl "https://staging.replicated.app/embedded/embedded-cluster-smoke-test-staging-app/ci-airgap/appver-dev-63330aa?airgap=true" -H "Authorization: $EC_SMOKE_TEST_LICENSE_ID" -o embedded-cluster-smoke-test-staging-app-ci.tgz

Happy debugging!

@emosbaugh emosbaugh force-pushed the emosbaugh/sc-118161/v1-to-v2-upgrades-e2e branch from 0ae391b to a741b5c Compare January 22, 2025 20:43
Comment on lines +476 to +478
build-upgrade-v2:
name: Build upgrade v2
runs-on: embedded-cluster-2
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why does this need to be an additional embedded cluster release? Is it being built differently than the normal upgrade version?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this tests a v2 to v2 upgrade after a v1 to v2 migration with the build-upgrade version. if it did not create a different ec release then it wouldnt be able to test a cluster upgrade.

@emosbaugh emosbaugh force-pushed the emosbaugh/sc-118161/v1-to-v2-upgrades-e2e branch 2 times, most recently from 620f997 to 4ecb468 Compare January 27, 2025 17:06
@emosbaugh emosbaugh force-pushed the emosbaugh/sc-118161/v1-to-v2-upgrades-e2e branch from a867a62 to 63330aa Compare January 28, 2025 00:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants