CloudBees Pipeline Explorer 1.20

Implemented the selected filters/lines highlighting feature.

The step badges are displayed in the log view when the Show steps option and related filters are active in the tree view. The related builds (build and triggerRemoteJob) and input steps are always displayed in the tree view, but the Show steps option must be activated to be displayed in the log view. The nodes are never displayed as badges in the log view.

Builds that had a large number of test failures recorded by the JUnit plugin performed poorly in the CloudBees Pipeline Explorer. The initial page load times were slow, and this can cause the web browser tab to crash. Performance has been improved by loading the test failures only when the test insights drawer is open, and truncating the failed tests shown in the CloudBees Pipeline Explorer to only the first 1000 failed tests. To see all of the failed tests, you can access the "Test Result" page that is linked from the CloudBees Pipeline Explorer test insights drawer.

When users clicked "Go to filtered log" in the CloudBees Pipeline Explorer map menu of a filtered node, the filter was being cleared out. Now, the filter is preserved and this issue has been resolved.

In the CloudBees Pipeline Explorer when the map and log were displayed at the same time, the menu of a node closed to the bottom of the map leading to a slight display jump.

The CloudBees Pipeline Explorer has performance issues when the tree displays a very large number of steps. The performance has been improved for the tree and the map.

In CloudBees Pipeline Explorer 1.17, the behavior of the Scroll to line door icon did not work. It originally cleared the active filter and scrolled down to the last line of the step that produced that error.

When opening the CloudBees Pipeline Explorer contextual menus, they unexpectedly closed when the mouse was moved in the map display.