Add line number extraction capability for error explanation

[Nikitaa104]

Summary

This PR introduces approximate line-number detection in the Explain Error plugin.
It enhances the extracted error logs by prefixing each matched line with its corresponding line number.

Why?

This aligns with the first improvement idea suggested by @trimarchimichael:
"Investigate if it is possible to add the line numbers, approx where the build fails in the explanation."

What’s Added?

• Line numbers appended during log extraction
• Cleaner and more informative error context
• Can assist users in identifying failing parts of pipeline logs faster

Checklist

• Tested locally
• Line numbers visible in error log extraction
• No breaking changes introduced

[panicking]

Was nice to be somehow link to the text. @mawinter69 any idea of possible?

[mawinter69]

I wonder it's not easier to just tell the AI to include information about the line numbers which it considers as the cause of the problem. Though one has to consider that the plugin isn't passing the complete log to the AI. By default it is I think the last 100 lines

[mawinter69]

To me the requirement is not totally clear.
@panicking Can you create an issue with a clear description what you expect here.

[panicking]

To me the requirement is not totally clear. @panicking Can you create an issue with a clear description what you expect here.

The idea is when you have a build explaination result is to be able to link from the explanation to the jenkins log. So understand where the failure reason is in the log console. Now what I said in the jenkins community is that I did not find an easy way to link <href or somenthing like that to go there. This allow not only to have an explanation by AI but confirm go down direct to the point where was analyzed. Is that more clear?

[panicking]

To me the requirement is not totally clear. @panicking Can you create an issue with a clear description what you expect here.

The idea is when you have a build explaination result is to be able to link from the explanation to the jenkins log. So understand where the failure reason is in the log console. Now what I said in the jenkins community is that I did not find an easy way to link <href or somenthing like that to go there. This allow not only to have an explanation by AI but confirm go down direct to the point where was analyzed. Is that more clear?

#60

[mawinter69]

Afaik you can't directly link to line numbers in Jenkins. There is https://plugins.jenkins.io/linenumbers/ that provides this.
Also as mentioned before the line numbers that are now extracted are the line numbers in the log snippet which is the last 100 lines. But what is not known here is how many lines are in the complete log. That can just b a few or some thousand lines. Also the AI would need to produce the link

[Nikitaa104]

Hi @panicking and @mawinter69,

I've rebased this PR on the latest upstream/main to include recent changes.

✅ Successfully merged with upstream
✅ Plugin builds cleanly
✅ Line number extraction feature remains intact
✅ All previous review feedback addressed

The PR is ready for final review. Please let me know if any additional changes are needed.

Thank you!

[mawinter69]

Would be interesting to see what the AI does with the line numbers. Is it using them in any way? Does it create any mentions that the error is in a specific line?

[shenxianpeng]

Also as mentioned before the line numbers that are now extracted are the line numbers in the log snippet which is the last 100 lines. But what is not known here is how many lines are in the complete log. That can just b a few or some thousand lines.

For this reason, and since PR #69 already addresses this by linking directly to the failed log section, I think this PR can be closed. Any thoughts?