Explain error plugin integration

[panicking]

What feature do you want to see added?

Hi all,

my idea is to allow to have a popup on the failing node that give the summary of the reason using the explain error plugin if this is activated and generate the error summary. I'm figure out what is the best option to show it, any idea is welcome

Upstream changes

No response

Are you interested in contributing this feature?

No response

[lemeurherve]

FTR, link to the plugin in question: https://plugins.jenkins.io/explain-error/

(Also, you have a typo in your issue title 😉)

[panicking]

FTR, link to the plugin in question: https://plugins.jenkins.io/explain-error/

(Also, you have a typo in your issue title 😉)

Thank you

[lemeurherve]

I'm figure out what is the best option to show it, any idea is welcome

How about a new row under the current stage one in case of error?

[panicking]

I'm figure out what is the best option to show it, any idea is welcome

How about a new row under the current stage one in case of error?

Sounds good

[KalleOlaviNiemitalo]

I hope this won't make explain-error-plugin a mandatory dependency of pipeline-graph-view-plugin.

Although explain-error-plugin doesn't work without an API key, and has a setting for disabling it altogether, it still feels like it increases the risk of build logs being exfiltrated to an AI provider not approved by the enterprise, so I'd prefer not having to install it at all.

[panicking]

I hope this won't make explain-error-plugin a mandatory dependency of pipeline-graph-view-plugin.

Although explain-error-plugin doesn't work without an API key, and has a setting for disabling it altogether, it still feels like it increases the risk of build logs being exfiltrated to an AI provider not approved by the enterprise, so I'd prefer not having to install it at all.

Absolutaly not, we can do just optional and it's show only if someone ask for it in the review

[mawinter69]

Ideally the dependency is from explain-error plugin to pipeline-graph view. For that we would need here an extension point. That would have the benefit that also other plugins can contribute if desired.

[panicking]

@mawinter69 I think the best is to add to FlowNode object a description, in the descripiton we can put failure reason and this can get populated by any plugin and then this plugin can render it. Is that somenthing that you like? Other point here is about how to manage what you propose? do you have an example where I can take a look?

[KalleOlaviNiemitalo]

There is documentation at

• Extensions
• Extensibility
• javadoc:
  • hudson.ExtensionList class
  • hudson.Extension annotation
  • hudson.ExtensionPoint interface
• and more in the zombified wiki, but that is out of date, like the warning banner says.

This plugin already implements some extensions for extension points defined elsewhere, but doesn't yet seem to define any extension points of its own.

[timja]

We try and define the extension points in core if possible and then plugins can implement them from there.
That way they can be used in more places than just this plugin.

It can start here though and be moved later if required.