Add deep link to AI Error Explanation UI

[panicking]

src: Add deep link to error log source in explanation UI

This commit introduces a "View Full Report" button within the AI Error
Explanation UI. This allows users to navigate directly from the AI
summary to the specific location of the failure.

Related to #61

[Copilot]

Pull request overview

This PR adds deep linking functionality to the AI Error Explanation UI, allowing users to navigate directly from the AI summary to the specific location of the failure in the build log or pipeline overview.

Key Changes

• Introduced PipelineLogExtractor class to extract logs from failed pipeline steps and generate appropriate URLs
• Updated ErrorExplanationAction to store and expose the URL for error source navigation
• Added "View Build Log" buttons in both the standalone explanation page and console footer UI

Reviewed changes

Copilot reviewed 13 out of 13 changed files in this pull request and generated 17 comments.

Show a summary per file

File	Description
src/main/java/io/jenkins/plugins/explain_error/PipelineLogExtractor.java	New class that extracts pipeline step logs and generates URLs to error sources, with optional pipeline-graph-view integration
src/main/java/io/jenkins/plugins/explain_error/ErrorExplanationAction.java	Added urlString field to store the error source URL and expose it via getter method
src/main/java/io/jenkins/plugins/explain_error/ErrorExplainer.java	Integrated PipelineLogExtractor to capture URLs during error log extraction
src/main/java/io/jenkins/plugins/explain_error/ConsoleExplainErrorAction.java	Updated to use PipelineLogExtractor and include URL in JSON response for AJAX requests
src/main/resources/io/jenkins/plugins/explain_error/ErrorExplanationAction/index.jelly	Added "View Build Log" button that links to the error source URL
src/main/resources/io/jenkins/plugins/explain_error/ConsolePageDecorator/footer.jelly	Added "View Build Log" button in the console footer explanation card
src/main/webapp/js/explain-error-footer.js	Updated to handle URL from JSON response and set href attribute on the link element
src/test/java/io/jenkins/plugins/explain_error/ErrorExplanationActionTest.java	Updated all test cases to use new constructor signature with urlString parameter
src/test/java/io/jenkins/plugins/explain_error/ErrorExplainerTest.java	Updated test cases to pass urlString parameter to explainErrorText method
src/test/java/io/jenkins/plugins/explain_error/ConsolePageDecoratorTest.java	Updated test to use new ErrorExplanationAction constructor signature
src/test/java/io/jenkins/plugins/explain_error/provider/TestProvider.java	Removed unused List import
src/main/java/io/jenkins/plugins/explain_error/ConsolePageDecorator.java	Removed unused StaplerRequest2 import
pom.xml	Added workflow-api, workflow-job, and pipeline-graph-view dependencies to support pipeline log extraction

Comments suppressed due to low confidence (1)

src/main/java/io/jenkins/plugins/explain_error/ErrorExplanationAction.java:31

• The urlString field is not initialized in the readResolve() method, which means it will be null when deserializing old ErrorExplanationAction instances that were saved before this field was added. This could cause NullPointerExceptions when accessing the URL in the UI. Consider initializing urlString to an empty string or a default console URL in readResolve().

    public Object readResolve() {
        if (providerName == null) {
            providerName = "Unknown";
        }
        return this;
    }

[shenxianpeng]

I’m not sure this is strictly necessary, since users can already click the "Pipeline Overview" button to reach the same page (it navigates to the failed step by default).

From a UI perspective, a couple of points to consider:

1. The button is quite long and behaves differently from other buttons—it resizes based on the window size.
2. There’s no spacing between this button and the AI Error Explanation section.

If it really needs it, it might be better to align its style with existing buttons. For example:

[panicking]

I’m not sure this is strictly necessary, since users can already click the "Pipeline Overview" button to reach the same page (it navigates to the failed step by default).

From a UI perspective, a couple of points to consider:

1. The button is quite long and behaves differently from other buttons—it resizes based on the window size.
2. There’s no spacing between this button and the AI Error Explanation section.

If it really needs it, it might be better to align its style with existing buttons. For example:

I like your idea but I'm not good in this, can you give me some help to make it nicer?

[panicking]

I’m not sure this is strictly necessary, since users can already click the "Pipeline Overview" button to reach the same page (it navigates to the failed step by default). From a UI perspective, a couple of points to consider:

1. The button is quite long and behaves differently from other buttons—it resizes based on the window size.
2. There’s no spacing between this button and the AI Error Explanation section.

If it really needs it, it might be better to align its style with existing buttons. For example:

I like your idea but I'm not good in this, can you give me some help to make it nicer?

In general the idea is to post the link of ExplainError to mattermost and user click the reaso of the error, and if they need to take a look of the error code they can then get the link direct from there

[panicking]

[shenxianpeng]

The image I shared earlier was taken from the current Jenkins UI

The new button you posted looks better. Compared with the existing UI style, there are a few alignment and consistency issues:

1. There’s no spacing between this button and the AI Error Explanation section.
2. The button's curvature is circular; a square shape would be preferable.
3. Refer to the current name in Jenkins(like View as plain text and View classic console); a name like "View failure output" (or something similar) might be more appropriate than the current name.

[panicking]

The image I shared earlier was taken from the current Jenkins UI

The new button you posted looks better. Compared with the existing UI style, there are a few alignment and consistency issues:

1. There’s no spacing between this button and the AI Error Explanation section.
2. The button's curvature is circular; a square shape would be preferable.
3. Refer to the current name in Jenkins(like View as plain text and View classic console); a name like "View failure output" (or something similar) might be more appropriate than the current name.

@shenxianpeng What about this change?

[panicking]

@shenxianpeng everything look ok but I need to drop maxLines = 100. I need to check because in general for gradle build of mobile applicaiton, the lines neeed are more then 100 but in the same time the number of token needed can exceed the ai max token

[shenxianpeng]

Sorry for the late reply. I’m currently on vacation and have limited time to try out the changes on my laptop.

At first glance, I noticed that you introduced a new CSS file, and I wasn’t sure whether this is something we’re expected to create ourselves.

[panicking]

Sorry for the late reply. I’m currently on vacation and have limited time to try out the changes on my laptop.

At first glance, I noticed that you introduced a new CSS file, and I wasn’t sure whether this is something we’re expected to create ourselves.

@shenxianpeng I get some of the type from the pipeline-graph view and icon is standard. @mawinter69 what is the right way here?

[mawinter69]

I think you should try with jenkins-button jenkins-!-destructive-color and remove your own class.
That way you ensure that you get consistent UI elements out of the box that work with other color themes, e.g. dark-theme.
See also Buttons in design library. You can also apply that to links

[panicking]

@mawinter69 done

[Copilot]

Pull request overview

Copilot reviewed 13 out of 13 changed files in this pull request and generated 6 comments.

Comments suppressed due to low confidence (1)

src/main/java/io/jenkins/plugins/explain_error/ErrorExplanationAction.java:31

• The readResolve method should handle backward compatibility for the new urlString field. When deserializing old ErrorExplanationAction instances that don't have the urlString field, it will be null. The method should initialize urlString to an empty string or a default value (like console URL) to prevent NullPointerException when the field is accessed in the UI templates.

    public Object readResolve() {
        if (providerName == null) {
            providerName = "Unknown";
        }
        return this;
    }