tests(ci): integrate upgrade tests into build_and_test.yml
#11783
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Previously, the upgrade tests were in a standalone workflow and used an incorrect container image as the upgrade target version. With this PR, the tests are integrated into the main build/test workflow and make use of the same container image as pongo, which is built from the PR's branch.
Adapted from https://github.com/Kong/kong-ee/pull/6853 - In EE, we already build a docker image for testing with Pongo, so it made sense to piggy-back the upgrade testing onto that. In CE, we don't have that, so the image is built specifically for the upgrade test.
Checklist
changelog/unreleased/kong
orskip-changelog
label added on PR if changelog is unnecessary. README.mdIssue reference
KAG-2804