-
Improvement
-
Resolution: Fixed
-
Minor
-
None
-
Jenkins 2.204.2
Our jenkins logs are growing very very large and very quickly and they're filled with these messages which:
1) is not very interesting to us (we limit the capacity on our agents)
2) prevent seeing other important error messages
3) makes us have to more frequently delete logs as they grow large too fast
Could there be some settings to prevent displaying these messages please? 
See screenshot
thanks!
[JENKINS-61084] Configure logs to not display "Template instance limit" message in jenkins logs
pjdarton
added a comment - Option? No; that's not the sort of thing that should be configurable. Log levels ought to be hard-coded ... but hard-coded to sensible defaults.
Looks like you're saying that they're not sensible; seems that you'd prefer these log messages to be logged at a less severe severity than "INFO"; feel free to submit a PR; it should only be a couple of lines difference.
pjdarton
added a comment - Option? No; that's not the sort of thing that should be configurable. Log levels ought to be hard-coded ... but hard-coded to sensible defaults.
Looks like you're saying that they're not sensible; seems that you'd prefer these log messages to be logged at a less severe severity than "INFO"; feel free to submit a PR; it should only be a couple of lines difference. 
Vincent Massol
added a comment - seems that you'd prefer these log messages to be logged at a less severe severity than "INFO";
Yes, debug logging would be good probably.
EDIT: Just checked and it seems it's been fixed already: https://github.com/jenkinsci/docker-plugin/commit/c3a38d7034132cb407832a4ae0372f44339a2b03#diff-0a438d5fa3c18711a9f82de9b72440c0R654
Strangely the issue's desc (https://github.com/jenkinsci/docker-plugin/pull/811) doesn't match the change but it's good that it was done!
Vincent Massol
added a comment - seems that you'd prefer these log messages to be logged at a less severe severity than "INFO";
Yes, debug logging would be good probably.
EDIT: Just checked and it seems it's been fixed already: https://github.com/jenkinsci/docker-plugin/commit/c3a38d7034132cb407832a4ae0372f44339a2b03#diff-0a438d5fa3c18711a9f82de9b72440c0R654
Strangely the issue's desc ( https://github.com/jenkinsci/docker-plugin/pull/811 ) doesn't match the change but it's good that it was done! Vincent Massol
added a comment - This issue can now be closed.
PS: I don't understand: is JIRA used as the issue tracker for docker-cloud plugin or is it github issues?
Vincent Massol
added a comment - This issue can now be closed.
PS: I don't understand: is JIRA used as the issue tracker for docker-cloud plugin or is it github issues? pjdarton
added a comment - Yes, I had to change those lines anyway, so I dropped the level from "INFO" to "FINE" while I was in there.
You are right that I didn't do it separately; according to my own rules, I should've done, but they're my rules so I get to ignore them if I wish 
As for issue tracking, it's a bit undefined... JIRA was here first; we can't really abandon JIRA. After the move to GitHub, github issues became an option, so they started being used too, without much of a clear strategy for either usecase.
Two things I am certain of is that (1) you can only do a pull-request via github and (2) neither should be used as a general helpdesk.
In an ideal world, we'd only have issues in JIRA and PRs in github ... but github PRs integrate with github issues better than they do with JIRA issues.
Either way, it works out much the same - I'll review PRs and merge them once I'm happy and mostly ignore everything else. In this case, you got lucky that I happened to be spending a couple of days working on the plugin and had seen this report and agreed with the suggestion.
pjdarton
added a comment - Yes, I had to change those lines anyway, so I dropped the level from "INFO" to "FINE" while I was in there.
You are right that I didn't do it separately; according to my own rules, I should've done, but they're my rules so I get to ignore them if I wish
As for issue tracking, it's a bit undefined... JIRA was here first; we can't really abandon JIRA. After the move to GitHub, github issues became an option, so they started being used too, without much of a clear strategy for either usecase.
Two things I am certain of is that (1) you can only do a pull-request via github and (2) neither should be used as a general helpdesk.
In an ideal world, we'd only have issues in JIRA and PRs in github ... but github PRs integrate with github issues better than they do with JIRA issues.
Either way, it works out much the same - I'll review PRs and merge them once I'm happy and mostly ignore everything else. In this case, you got lucky that I happened to be spending a couple of days working on the plugin and had seen this report and agreed with the suggestion. Vincent Massol
added a comment - thanks. 
Note: I google for this and couldn't find a solution, hence the jira issue. Maybe I should have posted on the forum...