-
Improvement
-
Resolution: Fixed
-
Minor
-
None
On a busy Jenkins controller, the service logs can have thousands of lines like this generated in a day:
2020-10-22 12:57:45.509+0000 [id=291063] INFO h.p.jira.JiraChangeLogAnnotator#annotate: Annotating Jira id: 'OPS-22386
This pollutes the logs and makes it hard to debug other problems. These logs should be using a lower level to reduce noise, as they are of limited value under normal circumstances.
[JENKINS-64988] 'Annotating Jira id' logs should be at a lower level
Description |
Original:
On a busy Jenkins controller, the service logs can have thousands of lines like this generated in a day:
{{2020-10-22 12:57:45.509+0000 [id=291063] INFO h.p.jira.JiraChangeLogAnnotator#annotate: Annotating Jira id: 'OPS-22386}} This pollutes the logs and makes it hard to debug other problems. These logs should be using a lower level to reduce noise, as they are of limited value under normal circumstances. |
New:
On a busy Jenkins controller, the service logs can have thousands of lines like this generated in a day:
{noformat} 2020-10-22 12:57:45.509+0000 [id=291063] INFO h.p.jira.JiraChangeLogAnnotator#annotate: Annotating Jira id: 'OPS-22386 {noformat} This pollutes the logs and makes it hard to debug other problems. These logs should be using a lower level to reduce noise, as they are of limited value under normal circumstances. |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Closed [ 6 ] |
Created https://github.com/jenkinsci/jira-plugin/pull/324 for this.
warden would you be the right assignee for this?