ci: publish report site after standard suite#101
Merged
Conversation
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.
Summary
summary.jsonandmetadata.jsonas GitHub artifactspublish-report-sitejob that runs after all shards, even when tests failpublish-report-site-static.mjs --uploadVerification
.github/workflows/e2e-standard.ymlgit diff --checkContext
The RC tag workflow now runs the VM suite, but without this job the immutable shard artifacts can upload while the static report-site index/sidebar remains stale until a manual publish. This closes the automatic run-and-publish path for future RC tags and merge-hsm pushes.