Currently it is not possible to create different reporter with the same parser: only t

This should work: <div class="snippet-clipboard-content notranslate position-relat

Allow different reporter to use the same parser about violation-comments-to-stash-plugin HOT 5 OPEN

jenkinsci commented on June 27, 2024

Allow different reporter to use the same parser

from violation-comments-to-stash-plugin.

Comments (5)

tomasbjerre commented on June 27, 2024

This should work:

violationConfigs: [
        [pattern: ".*/reports/lint-results-.*\\.xml\$", parser: 'ANDROIDLINT', reporter: "Lint ${flavor}"],
        [pattern: ".*/checkstyle/.*\\.xml\$|.*/reports/ktlint-results-.*\\.xml\$", parser: 'CHECKSTYLE', reporter: "Checkstyle or KtLint ${flavor}"],
        [pattern: '.*/findbugs/.*\\.xml\$', parser: 'FINDBUGS', reporter: "Findbugs ${flavor}"]
]

But I agree that it would be better to allow several reporters for the same parser!

from violation-comments-to-stash-plugin.

leinardi commented on June 27, 2024

Hey thanks for the workaround, I won't be able to test it before Thursday, but I'll report back.

from violation-comments-to-stash-plugin.

tomasbjerre commented on June 27, 2024

Another, not so pretty, workaround would be to use the plugin twice.

  step([
   $class: 'ViolationsToBitbucketServerRecorder', 
   config: [
   ...
    violationConfigs: [
        [pattern: ".*/reports/lint-results-.*\\.xml\$", parser: 'ANDROIDLINT', reporter: "Lint ${flavor}"],
        [pattern: ".*/checkstyle/.*\\.xml\$", parser: 'CHECKSTYLE', reporter: "Checkstyle ${flavor}"],
        [pattern: '.*/findbugs/.*\\.xml\$', parser: 'FINDBUGS', reporter: "Findbugs ${flavor}"],
   ]
  ])

  step([
   $class: 'ViolationsToBitbucketServerRecorder', 
   config: [
   ...
    violationConfigs: [
        [pattern: ".*/reports/ktlint-results-.*\\.xml\$", parser: 'CHECKSTYLE', reporter: "KtLint ${flavor}"],
   ]
  ])

from violation-comments-to-stash-plugin.

leinardi commented on June 27, 2024

This was my original idea but, again, I will be able to try it only on Thursday.

One question: is the second call of the plugin going to wipe the comments from the first call? Should I explicitly use keepOldComments: true?

from violation-comments-to-stash-plugin.

tomasbjerre commented on June 27, 2024

I would set keepOldComments: false in the first call and keepOldComments: true in the last one.

from violation-comments-to-stash-plugin.

Recommend Projects