-
Improvement
-
Resolution: Unresolved
-
Major
-
None
-
Jenkins:
ci.blueocean.io, which at the time of this writing is running 1.5.0-beta-3-SNAPSHOT (private-8257e63a-bouser) · Core 2.89.3 · 8257e63
Client:
Fedora Workstation 27, Chrome 65.0.3325.181,
Summary
When viewing a build result in Blue Ocean which includes code coverage reports (such as those from Jacoco), it's difficult to find the expected index.html files for each submodule. The user needs to click ""Show more" a lot of times to reveal everything, because it's presented in a flat list. Once done, the index.html files I expected to see, were not there, but they can be easily found from Classic.
Example use case
Karl the Quality Engineer would like to view code coverage reports for the Blue Ocean Pipeline Editor on each build done by ci.blueocean.io.
1. Cut a PR to Blue Ocean so that it'll get picked up by ci.blueocean.io. As of PR 1700 getting merged, which I did today, there should be code coverage reports available in the Artifacts tab.
4. For my particular use case, I was interested in viewing coverage reports for blueocean-pipeline-editor. When I first look at the Artifacts tab, though, no instances of the string "editor" are present:
5. Scroll all the way to the bottom, and click Show more. Another set of artifacts will be displayed, but still no instances of "editor":
6. Each time the user clicks "Show more,' the button stays anchored to the bottom of the list...but the list doesn't scroll. So to get back to the button, the user must scroll all the way to the bottom again.
7. I ended up clicking "Show more" eight times in total to reveal everything.
8. Once I had, I saw there was only one instance of index.html present:
9. Right click the "Go to classic" button and choose to open in a new tab, then switch to that tab. You'll be taken to the build result page for this same run:
10. Click "Build Artifacts," and you're taken to a brief list, broken down into folders.
11. The target folder for blueocean-pipeline-editor is easy to see and click on:
12. Once there, the code-coverage/report link is also easy to see:
13. Here's the index.html file I've been looking for:
14. Which looks like this. There's some images and whatnot missing, but the file is readable:
Very annoying, have to go back to the "regular" view in order to view artifacts