The CloudBees Pipeline Explorer plugin offers a streamlined approach to troubleshoot pipelines and view logs. This plugin was developed with a focus on performance to improve your experience for log viewing, whether your log files are 5MB or 500MB.
The Pipeline Explorer can visualize the stages of your Pipelines in a tree view that lets you filter the logs by stages. The log viewport can be customized with user preferences for line numbers, displaying ANSI colors from the log text, word wrapping, and custom time formats for timestamps.
The Pipeline Explorer also provides a search feature, so users can search large files without leaving the Pipeline Explorer interface.
To view a video introduction of the CloudBees Pipeline Explorer, you can watch the following video.
Install the CloudBees Pipeline Explorer Plugin
-
To find the plugin, go to Manage Jenkins > Plugins > Available Plugins and search for the CloudBees Pipeline Explorer.
-
Install the CloudBees Pipeline Explorer.
-
After the installation has completed, select
CloudBees Pipeline Explorerin the left navigation pane of the Pipeline builds to access the new functionality.
|
The CloudBees Pipeline Explorer only supports Pipeline builds that start after the plugin is installed and enabled. Beginning with CloudBees CI version 2.401.3.3 and higher, the plugin is automatically installed and enabled. |
How to set the CloudBees Pipeline Explorer as your default console output
To optionally set the CloudBees Pipeline Explorer as your default console output, go to your user menu in the upper right of the viewport and select Configure > Console URL Provider > Add > CloudBees Pipeline Explorer > Save. The following examples show the Configure option and the Console URL Provider option.
To route build links in notifications directly to the CloudBees Pipeline Explorer, go to your user menu in the upper right of the viewport and select Configure > Notification URL > CloudBees Pipeline Explorer > Save. The following example shows the Notification URL option.
Administrators can also set default values for the Console URL Provider option and the Notification URL option. To set the CloudBees Pipeline Explorer as the default console output, go to Manage Jenkins > Appearance > Console URL Provider > CloudBees Pipeline Explorer > Save. The following example shows the Console URL Provider administrator option.
To route build links in notifications directly to the CloudBees Pipeline Explorer, go to Manage Jenkins > System > Default notification URL > CloudBees Pipeline Explorer > Save. The following example shows the Notification URL administrator option.
Manage the CloudBees Pipeline Explorer
|
The CloudBees Pipeline Explorer has a light mode and a dark mode display option. To change the display modes, you can select them in the behavior preferences or the user preferences of your browser/OS. |
The following examples show the CloudBees Pipeline Explorer viewport. This displays the log information, the build information, and the preferences panel.
-
The build details that display the following information:
-
Build name and number
-
Build status
-
Build start time
-
Build duration
-
Can also display branch name and commit information
-
If the user has the required permissions, the following buttons may also be displayed:
-
A Rebuild button that rebuilds the completed builds
-
A Replay button that replays the completed builds
-
An Abort button that aborts the in-progress builds
-
-
-
Toolbar that displays the following information:
-
The File size or filter size
-
The Download button that downloads the log
-
The Replay button
-
The Expand icon (see N in Figure 1) that expands the log view to fullscreen mode.
-
-
View options:
-
The Map button that displays only the map
-
The Map and log button displays both the map and the log
-
The Log button displays only the log
-
-
Displays the following line information:
-
The navigation buttons that can jump to the first or last lines of the log to navigate through the log and search output.
-
Line number bar where you can enter the number of the line to highlight
-
-
Search bar with a filter option.
-
Expands/collapses the tree view.
-
The Star sets the drawer as your favorite. The favorite drawer is open by default.
-
The Times closes the tree drawer.
-
Unsuccessful steps panel that helps streamline troubleshooting.
-
Test insights that provide a summary of your test results and a list of the test failures
-
Build artifacts that let you directly access the build artifacts with a link to the build artifacts report
-
Related builds in the tree; displays the origin (parent) of the build and the builds triggered in the Pipeline.
-
Shortcuts that highlight the Pipeline Explorer keyboard global, map view, and log view navigation shortcuts as shown in the following figure.
Figure 7. CloudBees Pipeline Explorer shortcuts -
Expands/collapses the user preferences view (see Figure 8)
-
Link to CloudBees documentation
-
Search bar for the stages and step names.
-
The menu has the following options:
-
Show steps in branch
-
Activate filter
-
Copy filter URL
-
-
Console output
Figure 8. CloudBees Pipeline Explorer user preferences -
The customized user preferences panel (select the Settings icon) lets you personalize the build information, log view, map view, tree view, and behavior options.
|
The ANSI coloring state is not preserved across line boundaries. |
-
Display build information, such as build name, start time, duration, SCM information, build description, and queue time that shows the total amount of time of the build and all of its
nodesteps waiting in the queue.To reorder the preferences that display in the page header, select the Drag icon that is to the left of the preference name. -
Log view preferences, as follows:
-
Display line numbers
-
Display ANSI colors (supports ANSI escape sequences that specify 8-bit and 24-bit colors)
-
Wrap long lines
-
Display timestamps and their formats. The Pipeline Explorer Timezone uses the preferences in the Jenkins user profile. The timestamp pattern can be saved and the pattern reset to the default.
-
Limit the number of context badges. If disabled, all badges are displayed.
-
Scroll to the last line on load
-
Scroll to the cause of the failure on load
-
-
Map view preference, as follows:
-
Display the node steps. The menu for the node steps includes a View agent info button that brings you to the main page for that computer.
-
-
Tree view preferences, as follows:
-
Display the duration of each stage in the tree view if the
Show stage durationspreference is enabled -
Display the node steps in the tree if the
Show node stepspreference is enabled; displays agents or nodes in the tree view.
-
-
Behavior preferences, as follows:
-
Add a favorite display that opens by default; either log, map, or map and log.
-
Add a favorite view that includes one of the following: build artifacts, filter by tree view, none, related builds, test insights, or unsuccessful steps.
-
Display the theme options for the screen: dark, light, or match system theme (default). To activate the theme options, refresh your screen.
-
Search the logs
The CloudBees Pipeline Explorer can search the build logs within Jenkins.
|
For large log files (approximately 1 GB and larger), or for slow storage systems, a search may take several minutes to complete. If there are many searches that are run in parallel, they can cause serious controller-wide performance issues. By default, the CloudBees Pipeline Explorer does not allow you to search for more than 1 GB of log data at a single time. This limit can be adjusted by administrators in the system configuration for the CloudBees Pipeline Explorer. |
The search feature is case insensitive. When you enter a term in the search bar and press Enter, the CloudBees Pipeline Explorer searches the entire log file for the search term and returns all of the matching lines with the search term highlighted in each result. You can also select the Filter icon in the search bar to search only for filtered stage logs. The toolbar displays the total number of search results that were found.
If the search takes longer than the timeout of one minute, the request is canceled with a warning message.
The controller administrator can define a maximum file size for the search. If there is a search on a log or filter that is too large, the search is blocked.
You can also select the following search options:
-
Select Link
to copy a link for a specific line in the log to your clipboard -
Select GoTo
to display a specific line in the log in a new browser tab
The following example shows the search results for all logs with the Display colors preferences enabled.
Troubleshoot the pipeline errors
The unsuccessful steps panel helps streamline troubleshooting. This panel displays all of your pipeline errors, including errors that are not directly associated with any log lines. Each issue displays the stage and error message. If there is an associated log line, a go-to link is provided that can be shared.
The following examples show the unsuccessful steps panels.
-
Indicates the number of issues found
-
Stage label where the issue is found
-
Issue message
-
Collapse arrow that collapses the issue text
-
Door icon that displays the issue in the log
-
Indicates the number of issues found
-
Displays the failing tests with links that send the user to the JUnit test results page
-
Stage label where the issue is found
-
Issue message
-
Collapse arrow that collapses the issue text
-
Door icon that displays the issue in the log
Manage test results
The test insights panel is available in the Pipeline Explorer that is based on the JUnit test results. In this panel, users can find a summary of their test results and a list of test failures. Each failure includes the stage it was in and a link to that test in the JUnit plugin page. Users can also search for test and test class names, sort tests by name or duration, and display individual test results.
The following figure shows an example of the test insights display.
Analyze the build failures
The CloudBees Pipeline Explorer users that installed the Build Failure Analyzer (BFA) plugin can access a side panel and view indications that are found after a BFA scan and are also marked in the logs.
The Build Failure Analyzer (BFA) displays the results from the BFA plugin. It displays a list of identified problems and you can view the annotated lines that are updated in the log view. The identified problems display the name, description, categories configured in the BFA plugin, and the related lines in the build.
You can also select the Scan with Build Failure Analyzer option to access the failed BFA builds, where you can scan either the non-scanned builds (the default) or all of the recurrent builds.
The following figure shows an example of the BFA display.
Access build artifacts
The build artifacts allow you to directly access your build artifacts with a link to the build artifacts report. Build artifacts are the files produced by a build and they typically include the distribution packages, WAR files, reports, and log files.
The following figure shows an example of the build artifacts display.
View related builds
The related builds panel allows you to display the builds related to your current build. The tree view also displays the related builds in the stage in which the build was triggered. The related builds include the builds triggered in the current build and the origin (parent) build that triggered the current build.
The following figure shows an example of the related builds panel.
Autopoll
In the CloudBees Pipeline Explorer, when a build is in progress, you can enable autopolling to refresh the logs. If the related builds drawer is open, the related builds are also refreshed.
To configure autopolling, go to Jenkins > Manage Jenkins > System and enable the autopolling option.
CloudBees Pipeline Map
The CloudBees Pipeline Explorer Pipeline Map offers a revolutionary map view of your pipeline that enables a quick and intuitive understanding of its entire structure at a glance. This feature allows you to easily view the big picture and the sequence of stages that provide a visual alternative to traditional methods.
To view a video introduction of the CloudBees Pipeline Map, you can watch the following video.
The following example shows the CloudBees Pipeline Map.
-
View options, as follows:
-
The Map button that displays only the map
-
The Map and log button displays both the map and the log
-
The Log button displays only the log
-
-
Expand/collapse the tree view filter. When you expand the filter and search for a selected stage name, the stage name is highlighted on the map.
-
Zoom options, respectively, from top to bottom as follows:
-
Zoom in
-
Zoom out
-
Zoom to fit
-
Zoom to filter
-
-
Describes the cause of the build.
-
Stage name. The stage and all items enclosed within the solid line box indicate nested behavior. The top-down displays indicate parallel items and left-to-right stages indicate sequences.
-
Three-dot actions menu that has the Go to filtered log and Copy link to filtered log options.
-
Stages within a grey box denote parallel stages.
CloudBees Pipeline Map with deeply nested levels
If there are stages with deeply nested levels, you can expand or collapse the view. The following example displays deeply nested levels that are expanded.
For information about the CloudBees Pipeline Explorer plugin requirements and releases, refer to CloudBees Pipeline Explorer Plugin.