[JIRA] (JENKINS-52237) being able to configure a new parser with groovy script directly from the job configuration

[armandooooo@hotmail.com (JIRA)]

iostrym created an issue

Jenkins / JENKINS-52237 being able to configure a new parser with groovy script directly from the job configuration Issue Type: Improvement Assignee: Ulli Hafner Components: warnings-plugin Created: 2018-06-28 09:40 Environment: jenkins : 1.504 plug-in warning : 4.35 Priority: Major Reporter: iostrym we have several users and one admin. admin guy (myself) create some parser. it would be great if it could be possible for a user to choose a parser and being able to modify it (locally for its job). or even create a new one. because it is annoying to provide administrative right to users only for the parser creation. Add Comment

This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)

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

Ulli Hafner commented on JENKINS-52237

Re: being able to configure a new parser with groovy script directly from the job configuration It is in the admin section due to security reasons: the script can basically do anything on your system so it is only safe to be checked by an admin. I think we found a secure workaround for this: I will prohibit Groovy parsers to scan the console log. They are permitted only to scan files on the agent. Then only an agent might be compromised by a not well behaving script.

Add Comment

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

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

Ulli Hafner updated an issue

Jenkins / JENKINS-52237

being able to configure a new parser with groovy script directly from the job configuration

Change By: Ulli Hafner Component/s: warnings-ng-plugin Component/s: warnings-plugin

Add Comment

[medianick@gmail.com (JIRA)]

Nick Jones commented on JENKINS-52237

Re: being able to configure a new parser with groovy script directly from the job configuration The older Warnings plugin is the only way to define a custom console parser given this restriction – so this is a regression in functionality, blocking us from fully moving over to Warnings NG. Since the system-level parsers are able to be defined only by Jenkins administrators, how about allowing those parsers to access the console log while allowing job-level custom parsers to access only files in the workspace?

Add Comment

[ernst@ernstdehaan.com (JIRA)]

Ernst de Haan commented on JENKINS-52237

Re: being able to configure a new parser with groovy script directly from the job configuration

It would be nice if the parser would be configurable in a declarative manner. Then the security concerns would be alleviated and any job can just provide the configuration in a file.

Add Comment

[christopher.fenner@sap.com (JIRA)]

Christopher Fenner commented on JENKINS-52237

Re: being able to configure a new parser with groovy script directly from the job configuration

We need to parse the whole job log, so using tee is not an option for us. This is really blocking us from moving forward to warnings-ng plugin.

Add Comment

[christopher.fenner@sap.com (JIRA)]

Christopher Fenner commented on JENKINS-52237

Re: being able to configure a new parser with groovy script directly from the job configuration

For the old warnings plugin I could add a parser with  Jenkins.instance.getExtensionList(hudson.plugins.warnings.WarningsDescriptor.class).get(0).addGroovyParser(new hudson.plugins.warnings.GroovyParser(...)) How can this be done for the new warnings-ng plugin?

Add Comment

[christopher.fenner@sap.com (JIRA)]

Christopher Fenner edited a comment on JENKINS-52237

Re: being able to configure a new parser with groovy script directly from the job configuration

We need to parse the whole job log, so using tee is not an option for us. - This is really blocking us from moving forward to warnings-ng plugin. - This I can do now by fetching the log from the _currentBuild_ and writing it to a file.

Add Comment

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

Ulli Hafner commented on JENKINS-52237

Re: being able to configure a new parser with groovy script directly from the job configuration

This is not possible. Can't you add parsers using JCasC?

Add Comment

[christopher.fenner@sap.com (JIRA)]

Christopher Fenner commented on JENKINS-52237

Re: being able to configure a new parser with groovy script directly from the job configuration

CaaC was a good hint, I now use this to add a parser on the fly: def config = io.jenkins.plugins.analysis.warnings.groovy.ParserConfiguration.getInstance() config.setParsers( config.getParsers().plus( new io.jenkins.plugins.analysis.warnings.groovy.GroovyParser(id, name, regex, script, example) ) )

Add Comment

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

Ulli Hafner commented on JENKINS-52237

Re: being able to configure a new parser with groovy script directly from the job configuration

Good to see. Where or how do you execute that script? Are you interested in adding a small section for this approach in the documentation?

Add Comment

[christopher.fenner@sap.com (JIRA)]

Christopher Fenner commented on JENKINS-52237

Re: being able to configure a new parser with groovy script directly from the job configuration

We use this to position warnings/errors produced by pipeline shared library steps in pipeline runs more prominent on the job run by parsing with a custom message pattern. Sure, I'll have a look a the respective docs page.

Add Comment