-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
-
Blue Ocean - Candidates
I am sure cliffmeyers mentioned this to me, but I have noticed.
if you run a project, say like kzantow/failure-project, and write a long running pipeline that archives test failures early on in the pipeline - they do not show up in blue ocean until run completed.
In classic they are already visible.
Testing Notes:
- Will require an E2E test that runs a test with archived results in an earlier stage, confirm is shows up
[JENKINS-47044] Test failures that are archived while a build is still running don't show up until run is finished
Epic Link | New: JENKINS-36296 [ 172305 ] |
Sprint | Original: Blue Ocean 1.4 - candidates [ 326 ] | New: Blue Ocean 1.4 - beta 2 [ 416 ] |
Rank | New: Ranked higher |
Description |
Original:
I am sure [~cliffmeyers] mentioned this to me, but I have noticed. if you run a project, say like kzantow/failure-project, and write a long running pipeline that archives test failures early on in the pipeline - they do not show up in blue ocean until run completed. In classic they are already visible. |
New:
I am sure [~cliffmeyers] mentioned this to me, but I have noticed. if you run a project, say like kzantow/failure-project, and write a long running pipeline that archives test failures early on in the pipeline - they do not show up in blue ocean until run completed. In classic they are already visible. Testing Notes: * Will require an E2E test that runs a test with archived results in an earlier stage, confirm is shows up |
Sprint | Original: Blue Ocean 1.4 - beta 3 [ 416 ] | New: Blue Ocean 1.4 - beta 4 [ 441 ] |
michaelneale In your testing, do you know if you opened the Tests tab UI before the tests would have been archived in the pipeline, or after? Or does it make no difference?