fix: Use coverageKey from build metadata for coverage fetch#1546
Merged
fix: Use coverageKey from build metadata for coverage fetch#1546
Conversation
y-oksaku
approved these changes
Jan 16, 2026
yakanechi
approved these changes
Jan 19, 2026
minghay
approved these changes
Jan 20, 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.
Context
Coverage is not displayed in the v2 UI job list view because the
projectKeyparameter used in the coverage API call is incorrect.In the v1 UI,
projectKeyis derived from build metadata, which works correctly.Reference (v1 UI):
http://github.com/screwdriver-cd/ui/blob/a43b2c8a7a9a418c31de3e877d75bca201fa9680/app/components/pipeline-list-view/component.js#L288
Objective
Align the v2 UI with the v1 UI by setting
projectKeyfrom build metadata when calling the coverage API, so coverage is displayed correctly in the job list view.References
License
I confirm that this contribution is made under the terms of the license found in the root directory of this repository's source tree and that I have the authority necessary to make this contribution on behalf of its copyright owner.