Repository navigation
Point result links at the custom S3/GCS upload path - #4917
Merged
Merged
Conversation
When results were uploaded with --s3.path or --gcs.path, the links in Grafana/Graphite annotations, Slack and Matrix still pointed at the default domain/timestamp folder, so every link went to a page that didn't exist. The result URL now follows the same path the upload uses. Fixes #2330 Assisted-by: Claude Opus 5.5 noreply@anthropic.com
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.
When results were uploaded with --s3.path or --gcs.path, the links in Grafana/Graphite annotations, Slack and Matrix still pointed at the default domain/timestamp folder, so every link went to a page that didn't exist. The result URL now follows the same path the upload uses.
Fixes #2330
Assisted-by: Claude Opus 5.5 noreply@anthropic.com