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

test: simulate an upgrade in ci #3875

Merged
merged 2 commits into from
Feb 16, 2025
Merged

test: simulate an upgrade in ci #3875

merged 2 commits into from
Feb 16, 2025

Conversation

shreddedbacon
Copy link
Member

@shreddedbacon shreddedbacon commented Feb 3, 2025

General Checklist

  • Affected Issues have been mentioned in the Closing issues section
  • Documentation has been written/updated
  • PR title is ready for inclusion in changelog

Database Migrations

  • If your PR contains a database migation, it MUST be the latest in date order alphabetically

Description

The purpose of this is to install the latest stable release, and then perform an upgrade to the version in branch. This helps to validate if changes to Lagoon in either core, or the charts will cause a failure of an upgrade.

The process is to firstly install the latest stable release using the following (some extra options which may change with #3860)

make k3d/stable-local-stack

This will set up the k3d cluster, install the prerequisite components (ingress, harbor, etc) and then install the latest lagoon charts release versions (core, remote, build-deploy)

Once that is running, perform the upgrade using the following

make k3d/install-lagoon

This will just re-install, or upgrade, the core, remote, and build-deploy charts from the source repositories.

Also updated to allow for overriding the build-deploy-image without having to set the buildImage in the API. The build-deploy-image is now pulled and then pushed into the registry that is deployed as part of the local-stack and there are new make commands that can be used to push a different image into the registry to override it as required. This will hopefully allow for easier development and testing of build-deploy-images locally.

@shreddedbacon shreddedbacon force-pushed the stable-upgrade-jenkins branch 8 times, most recently from 62b7b64 to 4e54af2 Compare February 6, 2025 05:15
@shreddedbacon shreddedbacon force-pushed the stable-upgrade-jenkins branch 3 times, most recently from 0ee9968 to ca06e77 Compare February 9, 2025 22:56
@shreddedbacon shreddedbacon marked this pull request as ready for review February 10, 2025 02:39
# UI_IMAGE_REPO = uselagoon/ui
# UI_IMAGE_TAG =
UI_IMAGE_REPO = uselagoon/ui
UI_IMAGE_TAG = main
Copy link
Member

Choose a reason for hiding this comment

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

acknowledging that this override needs to stay here until the next stable release is out of the door to ensure Keycloak library backwards compatibility

@shreddedbacon shreddedbacon added this to the 2.24.0 milestone Feb 16, 2025
Copy link
Member

@tobybellwood tobybellwood left a comment

Choose a reason for hiding this comment

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

This looks good to me - doesn't add much to the test time, but an important step in checking upgrades.

@tobybellwood tobybellwood merged commit 3102fb5 into main Feb 16, 2025
2 checks passed
@shreddedbacon shreddedbacon deleted the stable-upgrade-jenkins branch February 17, 2025 02:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants