• Type: Bug
• Resolution: Fixed
• Priority: Minor
• Component/s: blueocean-plugin
• Labels:

  None
• Environment:

  Jenkins 2.117
  Blue Ocean 1.5

1. 

   screenshot-okay.png

   42 kB

   2018-07-06 08:33

2. 

   screenshot-bug.png

   28 kB

   2018-07-06 08:26

3. 

   04_Job2_Direct.png

   23 kB

   2018-05-03 15:39

4. 

   01_Job1.png

   74 kB

   2018-05-03 15:39

5. 

   03_Job2_Tests_Via_Job1.png

   32 kB

   2018-05-03 15:39

6. 

   05_Job2_Tests.png

   26 kB

   2018-05-03 15:39

7. 

   06_Job2_Tests.png

   33 kB

   2018-05-03 15:39

8. 

   02_Job2.png

   31 kB

   2018-05-03 15:39

[JENKINS-51111] Navigating to downstream job via Blue Ocean Triggered Builds does not show tests in Tests tab

Roger Wooley created issue - 2018-05-03 15:39

Roger Wooley made changes - 2018-05-03 15:41

Description

Original: Steps to reproduce using two jobs:  # First job: triggers the second job (wait = true)  # Second job: record unit tests  # Open Blue Ocean from the first job, click Triggered Builds to access the second job  # The Tests tab will say no results are recorded  # Exit Blue Ocean, and access it again from the second job  # The Tests tab will show results I noticed this happening both while the job was running and complete.

New: Steps to reproduce using two jobs:  * First job: triggers the second job (wait = true)  * Second job: record unit tests  * Open Blue Ocean from the first job, click Triggered Builds to access the second job  * The Tests tab will say no results are recorded  * Exit Blue Ocean, and access it again from the second job  * The Tests tab will show results I noticed this happening both while the job was running and complete.

Vivek Pandey made changes - 2018-05-14 22:17

Assignee

New: Josh McDonald [ sophistifunk ]

Collapse comment: Vivek Pandey added a comment - 2018-05-14 22:20

Vivek Pandey added a comment - 2018-05-14 22:20

Looks similar to https://issues.jenkins-ci.org/browse/JENKINS-51110.

Expand comment: Vivek Pandey added a comment - 2018-05-14 22:20

Vivek Pandey added a comment - 2018-05-14 22:20 Looks similar to https://issues.jenkins-ci.org/browse/JENKINS-51110 .

Josh McDonald made changes - 2018-05-22 07:13

Status

Original: Open [ 1 ]

New: In Progress [ 3 ]

Collapse comment: Josh McDonald added a comment - 2018-05-23 05:20

Josh McDonald added a comment - 2018-05-23 05:20

I can't replicate this, it works fine for me. Can anybody verify it?

Expand comment: Josh McDonald added a comment - 2018-05-23 05:20

Josh McDonald added a comment - 2018-05-23 05:20 I can't replicate this, it works fine for me. Can anybody verify it?

Collapse comment: Josh McDonald added a comment - 2018-05-23 05:22

Josh McDonald added a comment - 2018-05-23 05:22

I will go back to 1.5 and see if I can trigger it.

Expand comment: Josh McDonald added a comment - 2018-05-23 05:22

Josh McDonald added a comment - 2018-05-23 05:22 I will go back to 1.5 and see if I can trigger it.

Collapse comment: Josh McDonald added a comment - 2018-05-23 07:17

Josh McDonald added a comment - 2018-05-23 07:17

Can't replicate in 1.5 either

Expand comment: Josh McDonald added a comment - 2018-05-23 07:17

Josh McDonald added a comment - 2018-05-23 07:17 Can't replicate in 1.5 either

Josh McDonald made changes - 2018-05-23 07:46

Status

Original: In Progress [ 3 ]

New: Open [ 1 ]

Collapse comment: Roger Wooley added a comment - 2018-05-24 14:59

Roger Wooley added a comment - 2018-05-24 14:59

It only happens for the most recently ran job. If I perform the same steps on an older job it I can see the tests.

 

Expand comment: Roger Wooley added a comment - 2018-05-24 14:59

Roger Wooley added a comment - 2018-05-24 14:59 It only happens for the most recently ran job. If I perform the same steps on an older job it I can see the tests.  

Load more newer events