Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-57378

warnings-ng commands show up as General Build Step in pipeline views

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      At least the recordIssues command in a pipeline shows up as "General Build Step" when looking at the "Pipeline Steps" in the build details of a job.

      Moreover, the arguments of the step are not shown in the UI.

        Attachments

          Issue Links

            Activity

            Hide
            jfaust Jason Faust added a comment -

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

            Show
            jfaust Jason Faust added a comment - I'll work on generating an actual example of the bug, with input files, as soon as I get a chance.
            Hide
            drulli Ulli Hafner added a comment -

            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...

            Show
            drulli Ulli Hafner added a comment - 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...
            Hide
            drulli Ulli Hafner added a comment -

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

            Show
            drulli Ulli Hafner added a comment - In order to show the arguments one needs to override argumentsToString in the Descriptor.
            Hide
            kon Kalle Niemitalo added a comment -

            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.
            Show
            kon Kalle Niemitalo added a comment - 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.
            Hide
            drulli Ulli Hafner added a comment -

            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.

            Show
            drulli Ulli Hafner added a comment - 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.

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              jfaust Jason Faust
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: