[JIRA] (JENKINS-24463) PyLint parse missing errors

2018-12-14 Thread ullrich.haf...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner updated  JENKINS-24463  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-24463  
 
 
  PyLint parse missing errors   
 

  
 
 
 
 

 
Change By: 
 Ulli Hafner  
 
 
Status: 
 Fixed but Unreleased Resolved  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-24463) PyLint parse missing errors

2018-11-07 Thread ullrich.haf...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner updated  JENKINS-24463  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 I updated the help in the PyLint tool description.   
 

  
 
 
 
 

 
 Jenkins /  JENKINS-24463  
 
 
  PyLint parse missing errors   
 

  
 
 
 
 

 
Change By: 
 Ulli Hafner  
 
 
Status: 
 Open Fixed but Unreleased  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-24463) PyLint parse missing errors

2018-11-07 Thread ullrich.haf...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-24463  
 
 
  PyLint parse missing errors   
 

  
 
 
 
 

 
Change By: 
 Ulli Hafner  
 
 
Priority: 
 Major Minor  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-24463) PyLint parse missing errors

2018-11-07 Thread ullrich.haf...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-24463  
 
 
  PyLint parse missing errors   
 

  
 
 
 
 

 
Change By: 
 Ulli Hafner  
 
 
Component/s: 
 warnings-ng-plugin  
 
 
Component/s: 
 warnings-plugin  
 
 
Labels: 
 PR help - appreciated wanted newbie-friendly  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-24463) PyLint parse missing errors

2018-03-06 Thread sc...@schrecktech.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Scott Schreckengaust commented on  JENKINS-24463  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: PyLint parse missing errors   
 

  
 
 
 
 

 
 based on Ulli Hafner's reference of Łukasz Dudek above, here is the message format, pylint command, Pipeline step and console output that worked for Jenkins to report pylint messages through the Warnings plugin: ./pylintrc contains: 

 
 msg-template={path}:{line}: [{msg_id}, {obj}] {msg} ({symbol}) 

 Command: 

 
pylint --rcfile=./pylintrc CODE > pylint.log 

 Pipeline: 

 
step([$class: 'WarningsPublisher',
  parserConfigurations: [[
parserName: 'PyLint', pattern: '**/pylint*.log'
  ]],
  unstableTotalAll: '0', 
  usePreviousBuildAsReference: true
]) 

 Console: 

 
[WARNINGS] Parsing warnings in files '**/pylint-*.log' with parser PyLint
[WARNINGS] Searching for all files in WORKSPACE that match the pattern **/pylint-*.log
[WARNINGS] Parsing 1 file in WORKSPACE
[WARNINGS] Successfully parsed file WORKSPACE/pylint-py36.log with 2 unique warnings and 0 duplicates.
 

  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 T