Save run after explaining an error via the UI #54
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mawinter69
commented
Nov 5, 2025
| TaskListener listener = getContext().get(TaskListener.class); | ||
|
|
||
| // Add console explain error action to build (if not already present) | ||
| if (run.getAction(ConsoleExplainErrorAction.class) == null) { |
Contributor
Author
There was a problem hiding this comment.
Adding that action makes no sense. The factory will always add this action. Also for the step that action is not needed. It would only be persisted in the run without adding value.
shenxianpeng
added
the
bug
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fixes #53
Testing done
Interactive testing
Verified that after explaining an error via the UI and restarting Jenkins the explanation is still there.
Submitter checklist