Repository navigation
ci: run upgrade platform checks on the Azure blob store - #39306
Merged
Merged
Conversation
The Azurite platform checks only run the restart scenario, so nothing catches a Materialize upgrade that can no longer read blobs an earlier release wrote to Azure blob storage. Add Nightly steps that run the whole-Mz upgrade scenarios, from the last release and from the latest self-managed release, with the Azurite blob store. Co-Authored-By: Claude Opus 5.5 <[email protected]>
mtabebe
approved these changes
Sep 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Azurite platform checks only run the restart scenario in release qualification, so no CI job catches an upgrade that can no longer read blobs an earlier release wrote to Azure blob storage. This adds two Nightly steps that run the whole-Mz upgrade scenarios with
--features=azurite:UpgradeEntireMzfrom the last release, andUpgradeEntireMzFromLatestSelfManaged, which is the upgrade path Azure deployments take.StartMzalready passes the Azurite blob store to every version it starts, so the scenarios need no changes.Follow-up to the review of #39293, which moves persist's Azure backend to the new Azure SDK.
🤖 Generated with Claude Code