Identify that detecting violations from console/stage output is not supported (directly) about violation-comments-to-stash-plugin HOT 7 OPEN

Redirect to file first. This plugin only works with files.

from violation-comments-to-stash-plugin.

Forgot to add - all the examples specifically use filenames in pattern, but nothing in the documentation makes it clear that these are required, or that the default (empty) is not valid.

from violation-comments-to-stash-plugin.

Yes files are needed.

Will consider this a feature request to add error message if no file pattern supplied.

This should work if you want the console log as a file:
https://stackoverflow.com/questions/37386581/jenkins-console-output-log-location-in-filesystem

But it is possible that things that are not really violations, lines that accidentally have the same format, will be matched by the parsers if you parse the entire log.

from violation-comments-to-stash-plugin.

Thanks - at least one of my tools already produced a log-file so at least I have the basics running now.

Do you mind if I also add a separate enhancement request to (either) parse console log, or hook into "Analysis Model API" which is the basis of the "Warnings Next Generation Plugin" implementation that does file and/or console parsing as in recordIssues.

Are either ever likely to be supported?

from violation-comments-to-stash-plugin.

I think parsing the entire log will generate a lot of support issues with strange findings. Things that accidently match. So no I dont want that feature.

Hooking into Warnings is not going to happen. It would change the design too much. That plugin and this one are already sharing Violations Lib. I like my plugins to be as slim as possible and only contain Jenkins stuff. So that I can easily migrate workflows to another automation server if needed. Like creating maven/gradle plugins to do the same thing with Travis...

from violation-comments-to-stash-plugin.

@tomasbjerre
I'm Confused!

For ktlint and detekt your plugin really works like a charm and it's really cool work with it!

But i couldn't figure out yet how to get Kotlin Compiler Warnings working! :(

So you say the Violations Plugin requires files to parse for errors/warnings, but in the list of supported parsers for KotlinGradle it is noted "Output from Kotlin Gradle Plugin."
So do i need now to redirect the Gradle Output to a file first to use KotlinGradle plugin or can it read the Output on it's own???

Without a pattern it at least doesn't seem to work :-/

violationConfigs : [
    [parser: 'CHECKSTYLE', pattern: '.*/ktlint/.*\\.xml\$', reporter: 'ktlint'],
    [parser: 'CHECKSTYLE', pattern: '.*/detekt/.*\\.xml\$', reporter: 'detekt'],
    [parser: 'KOTLINGRADLE', reporter: 'KotlinGradle'] // not working
]

from violation-comments-to-stash-plugin.

@tomasbjerre Thanks for the quick reply.

With this configuration it works now:
Regarding your concern that the whole log is parsed, this way it only writes the log of compileKotlin task to a seperate file!

build.gradle.kts

tasks {
    compileKotlin {
        kotlinOptions {
            jvmTarget = "1.8"
        }
        // redirect output of task to file, required for violations plugin
        val taskOutput = StringBuilder()
        logging.addStandardOutputListener { taskOutput.append(it) }
        doLast {
            project.file("build/kotlin/compileKotlin.log").writeText(taskOutput.toString())
        }
    }
}

Jenkinsfile:

violationConfigs                      : [
    // Many more formats available, check https://github.com/tomasbjerre/violations-lib
    [parser: 'CHECKSTYLE', pattern: '.*/ktlint/.*\\.xml\$', reporter: 'ktlint'],
    [parser: 'CHECKSTYLE', pattern: '.*/detekt/.*\\.xml\$', reporter: 'detekt'],
    [parser: 'KOTLINGRADLE', pattern: '.*/kotlin/compileKotlin\\.log\$', reporter: 'KotlinGradle']
]

from violation-comments-to-stash-plugin.