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

[jfaust@tsunamit.com (JIRA)]

Jason Faust created an issue

Jenkins / JENKINS-57378 warnings-ng commands show up as General Build Step in pipeline views Issue Type: Bug Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2019-05-08 21:53 Priority: Trivial Reporter: Jason Faust 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. Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

[ullrich.hafner@gmail.com (JIRA)]

Ulli Hafner commented on JENKINS-57378

Re: warnings-ng commands show up as General Build Step in pipeline views And you don't want them to appear there? Or what exactly should be done? These are actually steps... I have for instnace: 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

Add Comment

[ullrich.hafner@gmail.com (JIRA)]

Ulli Hafner edited a comment on JENKINS-57378

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

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

I have for instnace instance : {noformat}

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

{noformat}

Add Comment

[jfaust@tsunamit.com (JIRA)]

Jason Faust commented on JENKINS-57378

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

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

Add Comment

[jfaust@tsunamit.com (JIRA)]

Jason Faust commented on JENKINS-57378

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

Fell free to close this as a bogus report.

Add Comment

[ullrich.hafner@gmail.com (JIRA)]

Ulli Hafner closed an issue as Cannot Reproduce

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

Jenkins / JENKINS-57378

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

Change By: Ulli Hafner Status: Open Closed Resolution: Cannot Reproduce

Add Comment

[jfaust@tsunamit.com (JIRA)]

Jason Faust edited a comment on JENKINS-57378

Re: warnings-ng commands show up as General Build Step in pipeline views 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: {code :text } 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 {code}

Add Comment

[jfaust@tsunamit.com (JIRA)]

Jason Faust commented on JENKINS-57378

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

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:

Unable to find source-code formatter for language: text. Available languages are: actionscript, ada, applescript, bash, c, c#, c++, cpp, css, erlang, go, groovy, haskell, html, java, javascript, js, json, lua, none, nyan, objc, perl, php, python, r, rainbow, ruby, scala, sh, sql, swift, visualbasic, xml, yaml

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

Add Comment

[jfaust@tsunamit.com (JIRA)]

Jason Faust reopened an issue

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

Jenkins / JENKINS-57378

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

Change By: Jason Faust Resolution: Cannot Reproduce Status: Closed Reopened

Add Comment

[ullrich.hafner@gmail.com (JIRA)]

Ulli Hafner commented on JENKINS-57378

Re: warnings-ng commands show up as General Build Step in pipeline views 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"?

Add Comment

[jfaust@tsunamit.com (JIRA)]

Jason Faust edited a comment on JENKINS-57378

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

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

Add Comment

[jfaust@tsunamit.com (JIRA)]

Jason Faust commented on JENKINS-57378

Re: warnings-ng commands show up as General Build Step in pipeline views It should be reading (I imagine) Record compiler warnings and static analysis results

Add Comment

[jfaust@tsunamit.com (JIRA)]

Jason Faust commented on JENKINS-57378

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

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

Add Comment

[ullrich.hafner@gmail.com (JIRA)]

Ulli Hafner commented on JENKINS-57378

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

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

Add Comment

[ullrich.hafner@gmail.com (JIRA)]

Ulli Hafner updated JENKINS-57378

Jenkins / JENKINS-57378

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

Change By: Ulli Hafner Status: Reopened Open

Add Comment

[ullrich.hafner@gmail.com (JIRA)]

Ulli Hafner commented on JENKINS-57378

Re: warnings-ng commands show up as General Build Step in pipeline views In order to show the arguments one needs to override argumentsToString in the Descriptor.

Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)

[ullrich.hafner@gmail.com (JIRA)]

Ulli Hafner assigned an issue to Unassigned

Jenkins / JENKINS-57378

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

Change By: Ulli Hafner Labels: help-wanted newbie-friendly Assignee: Ulli Hafner

Add Comment

[ullrich.hafner@gmail.com (JIRA)]

Ulli Hafner updated an issue

Jenkins / JENKINS-57378 warnings-ng commands show up as General Build Step in pipeline views Change By: Ulli Hafner

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.

Add Comment