And you don't want them to appear there? Or what exactly should be done? These are actually steps...

I have for instance:

Step	Arguments		Status
Start of Pipeline - (4 min 25 sec in block)			Success
Allocate node : Start - (4 min 25 sec in block)		Console Output	Success
Allocate node : Body : Start - (4 min 24 sec in block)			Success
Stage : Start - (7.8 sec in block)	Checkout	Console Output	Success
Checkout - (7.7 sec in block)			Success
Check out from version control - (7.6 sec in self)		Console Output	Success
Stage : Start - (4 min 16 sec in block)	Build and Analysis	Console Output	Success
Build and Analysis - (4 min 16 sec in block)			Success
Provide Maven environment : Start - (3 min 11 sec in block)		Console Output	Success
Provide Maven environment : Body : Start - (3 min 6 sec in block)			Success
Shell Script - (3 min 6 sec in self)	mvn -V -e clean verify -Dmaven.test.failure.ignore	Console Output	Success
Record compiler warnings and static analysis results - (22 sec in self)		Console Output	Success
Record compiler warnings and static analysis results - (8.5 sec in self)		Console Output	Success
Archive JUnit-formatted test results - (3.8 sec in self)	**/target/*-reports/TEST-*.xml	Console Output	Success
Record compiler warnings and static analysis results - (30 sec in self)		Console Output	Success

Alright, I'm seeing that now as well. I'm not sure where I saw the other message.

Fell free to close this as a bogus report.

Just had it pop up again.

Using Warnings-NG 5.0.0, analysis-model-api 5.0.2, Jenkins 2.164.3, and all the other plugins patched up to the version as of writing this note.

Note, had just did an inplace restart of Jenkins to patch analysis-model-api

But the output of the stage where I had all the static analysis bits in it looks like:

Stage : Start - (2 min 2 sec in block)	Static Analysis	Console Output	Success
Static Analysis - (2 min 2 sec in block)			Success
General Build Step - (24 sec in self)		Console Output	Success
General Build Step - (20 sec in self)		Console Output	Success
General Build Step - (18 sec in self)		Console Output	Success
General Build Step - (12 sec in self)		Console Output	Success
General Build Step - (15 sec in self)		Console Output	Success
General Build Step - (12 sec in self)		Console Output	Success
General Build Step - (16 sec in self)		Console Output	Success

I'll try to track this down better for debugging, but did see it happen again.

I must admit that I'm not really a pipeline user... I still have no clue where your output from above comes from and what are you expecting. Should there be something more specific than "General Build Step"?

It should be reading (I imagine) Record compiler warnings and static analysis results (for each line, all seven of those are recordIssues commands)

I'll work on generating an actual example of the bug, with input files, as soon as I get a chance.

I see. It would also make sense to see the actual arguments of the step. I have no idea how to set or change it...

In order to show the arguments one needs to override argumentsToString in the Descriptor.

Trying to figure out whether this issue has been fixed:

• "the arguments of the step are not shown in the UI" was fixed as JENKINS-62415.
• "General Build Step" doesn't seem to have been explicitly fixed, but I can't reproduce it either. I see "Record compiler warnings and static analysis results" in "Pipeline Steps" when using Jenkins 2.263.3 and Warnings Next Generation Plugin 8.8.0. If I understand correctly, the text comes from io.jenkins.plugins.analysis.core.steps.RecordIssuesStep.Descriptor#getDisplayName(). This issue was said to occur in Warnings-NG 5.0.0, which did not have RecordIssuesStep yet; but that version already had io.jenkins.plugins.analysis.core.steps.IssuesRecorder.Descriptor#getDisplayName() with an identical implementation.

We already discussed (in 2019) that the text "General Build Step" only sometimes occurs. It cannot reproduce that with the latests versions as well. So I think we can close this issue for now.