[JIRA] [log-parser-plugin] (JENKINS-27208) Add workflow compatibility to log-parser

5 views
Skip to first unread message

recena@gmail.com (JIRA)

unread,
Jul 9, 2015, 7:38:02 AM7/9/15
to jenkinsc...@googlegroups.com
Manuel Jesús Recena Soto assigned an issue to Manuel Jesús Recena Soto
 
Jenkins / New Feature JENKINS-27208
Add workflow compatibility to log-parser
Change By: Manuel Jesús Recena Soto
Assignee: rgoren Manuel Jesús Recena Soto
Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
Atlassian logo

recena@gmail.com (JIRA)

unread,
Jul 9, 2015, 7:38:05 AM7/9/15
to jenkinsc...@googlegroups.com
Status: Open In Progress

recena@gmail.com (JIRA)

unread,
Jul 9, 2015, 8:16:01 AM7/9/15
to jenkinsc...@googlegroups.com
Manuel Jesús Recena Soto updated an issue
highlighting * Highlighting  lines of interest in workflow logs (errors, warnings, information)
dividing * Dividing  the log into sections based on stages and parallel executions
displaying * Displaying  a summary of number of errors , warnings and information lines within the workflow log and its sections.
linking * Linking  the summary of errors and warnings into the context of the full workflow log, making it easy to find a line of interest in the log
showing * Showing  a summary of errors and warnings on the build page

recena@gmail.com (JIRA)

unread,
Aug 9, 2015, 3:57:05 PM8/9/15
to jenkinsc...@googlegroups.com
Status: In Progress Open

recena@gmail.com (JIRA)

unread,
Aug 11, 2015, 10:49:02 AM8/11/15
to jenkinsc...@googlegroups.com

recena@gmail.com (JIRA)

unread,
Aug 11, 2015, 10:49:02 AM8/11/15
to jenkinsc...@googlegroups.com
Status: Open In Progress

recena@gmail.com (JIRA)

unread,
Aug 14, 2015, 11:09:02 AM8/14/15
to jenkinsc...@googlegroups.com
Manuel Jesús Recena Soto updated an issue
Summary: Add workflow compatibility to log-parser Make Log Parser Plugin compatible with Workflow

nharniman@cloudbees.com (JIRA)

unread,
Sep 17, 2015, 10:02:04 AM9/17/15
to jenkinsc...@googlegroups.com

recena@gmail.com (JIRA)

unread,
Sep 17, 2015, 10:11:02 AM9/17/15
to jenkinsc...@googlegroups.com

recena@gmail.com (JIRA)

unread,
Sep 27, 2015, 5:23:01 PM9/27/15
to jenkinsc...@googlegroups.com

recena@gmail.com (JIRA)

unread,
Sep 30, 2015, 7:30:03 AM9/30/15
to jenkinsc...@googlegroups.com

Nigel Harniman The main source code modifications were done. I'm waiting the maintainer so that this PR can be merged.

scm_issue_link@java.net (JIRA)

unread,
Oct 13, 2015, 7:40:04 AM10/13/15
to jenkinsc...@googlegroups.com

Code changed in jenkins
User: recena
Path:
pom.xml
src/main/java/hudson/plugins/logparser/LogParserAction.java
src/main/java/hudson/plugins/logparser/LogParserParser.java
src/main/java/hudson/plugins/logparser/LogParserPublisher.java
src/main/java/hudson/plugins/logparser/LogParserStatusComputer.java
src/main/java/hudson/plugins/logparser/LogParserUtils.java
http://jenkins-ci.org/commit/log-parser-plugin/7847264fcf1605a4f1405ec8f7d53969d9430772
Log:
JENKINS-27208 Initial source code modifications

scm_issue_link@java.net (JIRA)

unread,
Oct 13, 2015, 7:40:05 AM10/13/15
to jenkinsc...@googlegroups.com

Code changed in jenkins
User: recena
Path:

src/main/java/hudson/plugins/logparser/LogParserPublisher.java
http://jenkins-ci.org/commit/log-parser-plugin/21247507ca6ddb85516272087d293cc6b7e7faf8
Log:
JENKINS-27208 DataBoundConstructor, DataBoundSetter

scm_issue_link@java.net (JIRA)

unread,
Oct 13, 2015, 7:40:07 AM10/13/15
to jenkinsc...@googlegroups.com

Code changed in jenkins
User: recena
Path:

src/main/java/hudson/plugins/logparser/LogParserParser.java
src/main/java/hudson/plugins/logparser/LogParserUtils.java
http://jenkins-ci.org/commit/log-parser-plugin/cc2c42ebcfa4b2bc9f5280b63a723803aec8b7dc
Log:
JENKINS-27208 InterruptedException is catched and relaunched as IOException

scm_issue_link@java.net (JIRA)

unread,
Oct 13, 2015, 7:40:07 AM10/13/15
to jenkinsc...@googlegroups.com

Code changed in jenkins
User: recena
Path:

src/main/java/hudson/plugins/logparser/LogParserPublisher.java
src/main/resources/hudson/plugins/logparser/LogParserPublisher/config.jelly
http://jenkins-ci.org/commit/log-parser-plugin/e59455cd109db00d8a6b4b3174b2ec3a77e86b9f
Log:
JENKINS-27208 Removed obsolete way to work

scm_issue_link@java.net (JIRA)

unread,
Oct 13, 2015, 7:40:09 AM10/13/15
to jenkinsc...@googlegroups.com

Code changed in jenkins
User: Manuel Recena
Path:
src/main/java/hudson/plugins/logparser/LogParserPublisher.java
src/test/java/org/jenkinsci/plugins/logparser/LogParserWorkflowTest.java
src/test/resources/org/jenkinsci/plugins/logparser/maven-project1.zip
http://jenkins-ci.org/commit/log-parser-plugin/95a68a050a5a3f7df392c0c98eea3edbe854c316
Log:
JENKINS-27208 Added a test specific for workflow compatibility

scm_issue_link@java.net (JIRA)

unread,
Oct 13, 2015, 7:40:09 AM10/13/15
to jenkinsc...@googlegroups.com

scm_issue_link@java.net (JIRA)

unread,
Oct 13, 2015, 7:40:10 AM10/13/15
to jenkinsc...@googlegroups.com

scm_issue_link@java.net (JIRA)

unread,
Oct 13, 2015, 7:40:10 AM10/13/15
to jenkinsc...@googlegroups.com

Code changed in jenkins
User: recena
Path:
src/test/java/org/jenkinsci/plugins/logparser/LogParserWorkflowTest.java
http://jenkins-ci.org/commit/log-parser-plugin/87922996bfb1d7474bb4c1c5ac6e93ef46399855
Log:
JENKINS-27208 @amuniz's comments were addressed

scm_issue_link@java.net (JIRA)

unread,
Oct 13, 2015, 7:40:12 AM10/13/15
to jenkinsc...@googlegroups.com

Code changed in jenkins
User: Manuel Recena
Path:
src/main/java/hudson/plugins/logparser/LogParserPublisher.java
http://jenkins-ci.org/commit/log-parser-plugin/4fcb6fb40efcb7694d4b4944b1941005cb863611
Log:
JENKINS-27208 A variable has been renamed to reduce the changes (diff)

scm_issue_link@java.net (JIRA)

unread,
Oct 13, 2015, 7:40:12 AM10/13/15
to jenkinsc...@googlegroups.com

Code changed in jenkins
User: Manuel Recena
Path:

src/main/java/hudson/plugins/logparser/LogParserParser.java
http://jenkins-ci.org/commit/log-parser-plugin/b1a2956236c38edc5e4b4ec8c02dddaad2f0d35e
Log:
JENKINS-27208 Removed an unnecessary method

scm_issue_link@java.net (JIRA)

unread,
Oct 13, 2015, 7:40:15 AM10/13/15
to jenkinsc...@googlegroups.com

Code changed in jenkins
User: Manuel Recena
Path:

pom.xml
src/main/java/hudson/plugins/logparser/LogParserAction.java
src/main/java/hudson/plugins/logparser/LogParserParser.java
src/main/java/hudson/plugins/logparser/LogParserPublisher.java
src/main/java/hudson/plugins/logparser/LogParserStatusComputer.java
src/main/java/hudson/plugins/logparser/LogParserUtils.java

src/main/resources/hudson/plugins/logparser/LogParserPublisher/config.jelly
src/test/java/org/jenkinsci/plugins/logparser/LogParserWorkflowTest.java
src/test/resources/org/jenkinsci/plugins/logparser/maven-project1.zip
http://jenkins-ci.org/commit/log-parser-plugin/7cce02101fab53f4ba7ce25c03c4a170f475e8ee
Log:
Merge pull request #10 from recena/JENKINS-27208

JENKINS-27208 Compatible with Workflow

Compare: https://github.com/jenkinsci/log-parser-plugin/compare/398c0efd775d...7cce02101fab

recena@gmail.com (JIRA)

unread,
Oct 13, 2015, 7:41:03 AM10/13/15
to jenkinsc...@googlegroups.com
Manuel Jesús Recena Soto resolved as Done
 
Status: In Progress Resolved
Resolution: Done

scm_issue_link@java.net (JIRA)

unread,
Oct 20, 2015, 11:34:10 AM10/20/15
to jenkinsc...@googlegroups.com

Code changed in jenkins
User: Jesse Glick
Path:
COMPATIBILITY.md
http://jenkins-ci.org/commit/workflow-plugin/750a2bddca1cf7814a8bbf1e773a4ade4b9b7db9
Log:
Merge pull request #224 from recena/master

JENKINS-27208 Compatibility listing updated

Compare: https://github.com/jenkinsci/workflow-plugin/compare/55e78e84aad5...750a2bddca1c

sorin.sbarnea@gmail.com (JIRA)

unread,
Aug 17, 2016, 7:40:03 AM8/17/16
to jenkinsc...@googlegroups.com
Sorin Sbarnea reopened an issue
 

Sorry for re-opening this bug but adding support for the Workflow without documenting it on the plugin homepage seems like a good reasons to consider this feature not fully implemented.

I would not mind editing the the https://wiki.jenkins-ci.org/display/JENKINS/Log+Parser+Plugin page and adding the information related to Workflow usage but I don't know yet which is this information.

Once I have a simple pipeline code example I would add it to the wiki.

Change By: Sorin Sbarnea
Resolution: Done
Status: Resolved Reopened
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
Atlassian logo

manish_king@yahoo.com (JIRA)

unread,
Aug 17, 2016, 10:59:11 AM8/17/16
to jenkinsc...@googlegroups.com
Manish Patel commented on New Feature JENKINS-27208
 
Re: Make Log Parser Plugin compatible with Workflow

I agree with Sorin Sbarnea above.
An example would help a great deal for beginners.

Thanks in advance.

xouthier@yahoo.fr (JIRA)

unread,
Jan 23, 2017, 2:03:02 PM1/23/17
to jenkinsc...@googlegroups.com
X O commented on New Feature JENKINS-27208

Please, be nice and document how to use it with pipeline on the page of the plug-in.

Thanks a lot.

warrence.stm@gmx.de (JIRA)

unread,
Apr 14, 2020, 3:24:05 PM4/14/20
to jenkinsc...@googlegroups.com

There seems to be an error in the snippet generated for logParser in the Pipeline Syntax page. I generated the snippet

logParser parsingRulesPath: 'D:\\Jenkins_Log_Parser_Files\\my_global_parse_rule', useProjectRule: false

which gives me the error

WorkflowScript: 73: Missing required parameter: "projectRulePath" @ line 73, column 13.
               logParser parsingRulesPath: 'D:\\Jenkins_Log_Parser_Files\\my_global_parse_rule', useProjectRule: false
               ^

Adding

, projectRulePath: ''

to the end of the snippet fixes this error.

In addition, why is the path in the logParser call instead of the name of the rule, as specified in a none-pipeline job or in the snippet generator itself? This will be hell for me if the drive location of the global log parser rule ever changes...

Thanks.

PS: Up-to-date documentation is always useful.

This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
Atlassian logo

warrence.stm@gmx.de (JIRA)

unread,
Apr 23, 2020, 6:25:03 AM4/23/20
to jenkinsc...@googlegroups.com
Stefan Müller edited a comment on New Feature JENKINS-27208
There seems to be an error in the snippet generated for {{logParser}} in the Pipeline Syntax page. I generated the snippet
{code:groovy}
logParser parsingRulesPath: 'D:\\Jenkins_Log_Parser_Files\\my_global_parse_rule', useProjectRule: false{code}

which gives me the error
{code:none}

WorkflowScript: 73: Missing required parameter: "projectRulePath" @ line 73, column 13.
               logParser parsingRulesPath: 'D:\\Jenkins_Log_Parser_Files\\my_global_parse_rule', useProjectRule: false
               ^{code}
Adding
{code:none}
, projectRulePath: ''{code}

to the end of the snippet fixes this error.

In addition, why is the path in the {{logParser}} call instead of the name of the rule, as specified in a none-pipeline job or in the snippet generator itself? This will be hell for me if the drive location of the global log parser rule ever changes...

Thanks.

PS: Up I know it's a lot of work to keep this stuff up -to-date , but IMHO, further documentation is always useful. ;- needed (not just for this plugin ) . E. g. there is an option {{showGraphs}} with no explanation. I tried it, hoping it might give me maybe parsing on step level, and found no effect.

warrence.stm@gmx.de (JIRA)

unread,
Apr 23, 2020, 6:25:10 AM4/23/20
to jenkinsc...@googlegroups.com
Stefan Müller edited a comment on New Feature JENKINS-27208
There seems to be an error in the snippet generated for {{logParser}} in the Pipeline Syntax page. I generated the snippet
{code:groovy}
logParser parsingRulesPath: 'D:\\Jenkins_Log_Parser_Files\\my_global_parse_rule', useProjectRule: false{code}
which gives me the error
{code:none}
WorkflowScript: 73: Missing required parameter: "projectRulePath" @ line 73, column 13.
               logParser parsingRulesPath: 'D:\\Jenkins_Log_Parser_Files\\my_global_parse_rule', useProjectRule: false
               ^{code}
Adding
{code:none}
, projectRulePath: ''{code}
to the end of the snippet fixes this error.

In addition, why is the path in the {{logParser}} call instead of the name of the rule, as specified in a none-pipeline job or in the snippet generator itself? This will be hell for me if the drive location of the global log parser rule ever changes...

Thanks.

PS: I know it's a lot of work to keep this stuff up-to-date, but IMHO, further documentation is needed (not just for this plugin). E. g. there is an option {{showGraphs}} (https://jenkins.io/doc/pipeline/steps/log-parser/) with no explanation. I tried it, hoping it might give me maybe parsing on step level, and found no effect.
Reply all
Reply to author
Forward
0 new messages