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

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

XMLWordPrintable

      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.

          [JENKINS-57378] warnings-ng commands show up as General Build Step in pipeline views

          Jason Faust created issue -

          Ulli Hafner added a comment - - edited

          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

          Ulli Hafner added a comment - - edited 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

          Jason Faust added a comment -

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

          Jason Faust added a comment - Alright, I'm seeing that now as well. I'm not sure where I saw the other message.

          Jason Faust added a comment -

          Fell free to close this as a bogus report.

          Jason Faust added a comment - Fell free to close this as a bogus report.

          Ulli Hafner added a comment -

          Ok, I'm closing it. If you see it a again please reopen and provide a pointer to the wrong message.

          Ulli Hafner added a comment - Ok, I'm closing it. If you see it a again please reopen and provide a pointer to the wrong message.
          Ulli Hafner made changes -
          Resolution New: Cannot Reproduce [ 5 ]
          Status Original: Open [ 1 ] New: Closed [ 6 ]

          Jason Faust added a comment - - edited

          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

          Jason Faust added a comment - - edited 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

          Jason Faust added a comment -

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

          Jason Faust added a comment - I'll try to track this down better for debugging, but did see it happen again.
          Jason Faust made changes -
          Resolution Original: Cannot Reproduce [ 5 ]
          Status Original: Closed [ 6 ] New: Reopened [ 4 ]

          Ulli Hafner added a comment -

          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"?

          Ulli Hafner added a comment - 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"?

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

              Created:
              Updated:
              Resolved: