Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-48066

Activity tab for multibranch pipeline doesn't display new runs when branch filtering is active

      When viewing the Activity tab for a multibranch pipeline, the runs list will not update with new runs while branch filtering is active. This might only apply to branches that contain slashes in the name.

      Repro Steps

      1. Open activity tab for a multibranch pipeline in two different tabs
        1. Note that this might be more reproducible using branches with git-flow naming style
      2. In Tab B, replay a branch. Note that in Tab A, the run appears.
      3. In Tab A, apply filtering for that branch.
      4. In Tab B, replay that branch again. Note the run appears in Tab B.

      Expected Behavior

      • Second run should appear in Tab A

      Actual Behavior

      • Second run does not appear in Tab B.
        • Note that clearing the branch filter should display the run that was previously hidden.

      Notes

      • You can probably do this testing in a single tab and still see the issue.
      • Might be able to write a unit test for this against the Activity component but may be challenging.
      • ATH shouldn't be too difficult to write.

        1. screenshot-10.png
          screenshot-10.png
          495 kB
        2. screenshot-9.png
          screenshot-9.png
          490 kB
        3. screenshot-8.png
          screenshot-8.png
          503 kB
        4. screenshot-7.png
          screenshot-7.png
          387 kB
        5. screenshot-6.png
          screenshot-6.png
          334 kB
        6. screenshot-5.png
          screenshot-5.png
          466 kB
        7. screenshot-4.png
          screenshot-4.png
          441 kB
        8. screenshot-3.png
          screenshot-3.png
          332 kB
        9. screenshot-2.png
          screenshot-2.png
          436 kB
        10. screenshot-1.png
          screenshot-1.png
          442 kB

          [JENKINS-48066] Activity tab for multibranch pipeline doesn't display new runs when branch filtering is active

          Cliff Meyers created issue -
          Cliff Meyers made changes -
          Epic Link New: JENKINS-35742 [ 171802 ]
          Cliff Meyers made changes -
          Description Original: When viewing the Activity tab for a multibranch pipeline, the runs list will not update with new runs while branch filtering is active.

          *Repro Steps*
          # Open activity tab for a multibranch pipeline in two different tabs
          ## Note that this might be more reproducible using branches with git-flow naming style
          # In Tab B, replay a branch. Note that in Tab A, the run appears.
          # In Tab A, apply filtering for that branch.
          # In Tab B, replay that branch again. Note the run appears in Tab B.

          *Expected Behavior*
          * Second run should appear in Tab A

          *Actual Behavior*
          * Second run does not appear in Tab B.
          ** Note that clearing the branch filter should display the run that was previously hidden.

          *Notes*
          * You can probably do this testing in a single tab and still see the issue.
          * Might be able to write a unit test for this against the Activity component but may be challenging.
          * ATH shouldn't be too difficult to write.
          New: When viewing the Activity tab for a multibranch pipeline, the runs list will not update with new runs while branch filtering is active. This might only apply to branches that contains slashes in the name.

          *Repro Steps*
          # Open activity tab for a multibranch pipeline in two different tabs
          ## Note that this might be more reproducible using branches with git-flow naming style
          # In Tab B, replay a branch. Note that in Tab A, the run appears.
          # In Tab A, apply filtering for that branch.
          # In Tab B, replay that branch again. Note the run appears in Tab B.

          *Expected Behavior*
          * Second run should appear in Tab A

          *Actual Behavior*
          * Second run does not appear in Tab B.
          ** Note that clearing the branch filter should display the run that was previously hidden.

          *Notes*
          * You can probably do this testing in a single tab and still see the issue.
          * Might be able to write a unit test for this against the Activity component but may be challenging.
          * ATH shouldn't be too difficult to write.
          Cliff Meyers made changes -
          Description Original: When viewing the Activity tab for a multibranch pipeline, the runs list will not update with new runs while branch filtering is active. This might only apply to branches that contains slashes in the name.

          *Repro Steps*
          # Open activity tab for a multibranch pipeline in two different tabs
          ## Note that this might be more reproducible using branches with git-flow naming style
          # In Tab B, replay a branch. Note that in Tab A, the run appears.
          # In Tab A, apply filtering for that branch.
          # In Tab B, replay that branch again. Note the run appears in Tab B.

          *Expected Behavior*
          * Second run should appear in Tab A

          *Actual Behavior*
          * Second run does not appear in Tab B.
          ** Note that clearing the branch filter should display the run that was previously hidden.

          *Notes*
          * You can probably do this testing in a single tab and still see the issue.
          * Might be able to write a unit test for this against the Activity component but may be challenging.
          * ATH shouldn't be too difficult to write.
          New: When viewing the Activity tab for a multibranch pipeline, the runs list will not update with new runs while branch filtering is active. This might only apply to branches that contain slashes in the name.

          *Repro Steps*
          # Open activity tab for a multibranch pipeline in two different tabs
          ## Note that this might be more reproducible using branches with git-flow naming style
          # In Tab B, replay a branch. Note that in Tab A, the run appears.
          # In Tab A, apply filtering for that branch.
          # In Tab B, replay that branch again. Note the run appears in Tab B.

          *Expected Behavior*
          * Second run should appear in Tab A

          *Actual Behavior*
          * Second run does not appear in Tab B.
          ** Note that clearing the branch filter should display the run that was previously hidden.

          *Notes*
          * You can probably do this testing in a single tab and still see the issue.
          * Might be able to write a unit test for this against the Activity component but may be challenging.
          * ATH shouldn't be too difficult to write.

          Cliff Meyers added a comment -

          cc kshultz curious whether you can repro this, and feel free to add additional testing notes.

          Cliff Meyers added a comment - cc kshultz curious whether you can repro this, and feel free to add additional testing notes.
          Karl Shultz made changes -
          Attachment New: screenshot-1.png [ 40418 ]
          Karl Shultz made changes -
          Attachment New: screenshot-2.png [ 40419 ]
          Karl Shultz made changes -
          Attachment New: screenshot-3.png [ 40420 ]
          Karl Shultz made changes -
          Attachment New: screenshot-4.png [ 40421 ]

          Karl Shultz added a comment - - edited

          cliffmeyers - I've tried this now, and can confirm some simliar behaviors with filtering, but for me, it's the opposite. Applying a filter shows the runs, and removing it deletes them. Here's how I did it.

          Environment:

          • Blue Ocean 1.3.2, Jenkins core 2.89
          • "Tab B" is the rightmost tab in these screenshots. "Tab A" is second-from-rightmost.

          1. I've got a repo on GitHub Enterprise, and just saved its Jenkinsfile to a new branch, which I called "48066." Shown here on Tab B are its first run, and the replay:

          2. On Tab A, only the initial run gets displayed. Not only that, it's still animating, as if it's building still:

          3. Applying a filter to Tab A (the one with the missing run), reveals the second run. And it updates the status of both of them to where they're no longer animating:

          4. But when I clear the filter on Tab A, the run which used to be visible while the filter was applied, is gone again:

          I think you're right, that an ATH test would be pretty easy to implement.

          Great find.

          Karl Shultz added a comment - - edited cliffmeyers - I've tried this now, and can confirm some simliar behaviors with filtering, but for me, it's the opposite. Applying a filter shows the runs, and removing it deletes them. Here's how I did it. Environment: Blue Ocean 1.3.2, Jenkins core 2.89 "Tab B" is the rightmost tab in these screenshots. "Tab A" is second-from-rightmost. 1. I've got a repo on GitHub Enterprise, and just saved its Jenkinsfile to a new branch, which I called "48066." Shown here on Tab B are its first run, and the replay: 2. On Tab A, only the initial run gets displayed. Not only that, it's still animating, as if it's building still: 3. Applying a filter to Tab A (the one with the missing run), reveals the second run. And it updates the status of both of them to where they're no longer animating: 4. But when I clear the filter on Tab A, the run which used to be visible while the filter was applied, is gone again: I think you're right, that an ATH test would be pretty easy to implement. Great find.

            Unassigned Unassigned
            cliffmeyers Cliff Meyers
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: