-
Improvement
-
Resolution: Not A Defect
-
Minor
-
None
-
Virtualized Ubuntu Server 12.04 host
When the number of lint warnings increase for a build, our team would like to send out a notification to the team. In our model, there should never be new issues as these tools are supposed to be run prior to committing changes to the repository. We want the user's name in lights if they don't follow protocol.
For pylint, I do this by parsing the pylint.xml output file, but since we use a jslint plugin for the actual jslint run, I have no way to do this. Besides, I'd rather have one way of doing this no matter what lint or warnings are being processed. For consistency, I thought it would just be great if the warnings plugin could provide an option to email out for increases in the number of lint issues. That's what we'd prefer, but someone else might make the case that email only goes out if the last build was unstable (i.e. we reached a certain number of lint issues at a specific severity).
[JENKINS-19295] Option to send email when the # of jslint/pylint warnings increase
| Description |
Original:
When the number of lint warnings increase for a build, our team would like to send out a notification to the team. In our model, there should never be new issues as these tools are supposed to be run prior to committing changes to the repository. We want the user's name in lights if they don't follow protocol. For pylint, I do this by parsing the pylint.xml output file, but since we use a jslint plugin for the actual jslint run, I have no way to do this. For consistency, I thought it would just be great if the warnings plugin could provide an option to email out for increases in the number of lint issues. That's what we'd prefer, but someone else might make the case that email only goes out if the last build was unstable (i.e. we reached a certain number of lint issues at a specific severity). |
New:
When the number of lint warnings increase for a build, our team would like to send out a notification to the team. In our model, there should never be new issues as these tools are supposed to be run prior to committing changes to the repository. We want the user's name in lights if they don't follow protocol. For pylint, I do this by parsing the pylint.xml output file, but since we use a jslint plugin for the actual jslint run, I have no way to do this. Besides, I'd rather have one way of doing this no matter what lint or warnings are being processed. For consistency, I thought it would just be great if the warnings plugin could provide an option to email out for increases in the number of lint issues. That's what we'd prefer, but someone else might make the case that email only goes out if the last build was unstable (i.e. we reached a certain number of lint issues at a specific severity). |
| Resolution | New: Not A Defect [ 7 ] | |
| Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
| Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
| Workflow | Original: JNJira [ 150743 ] | New: JNJira + In-Review [ 206889 ] |