Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FIXED JENKINS-21386] Allow reordering loggers, use first with matching ... #1091

Merged
merged 1 commit into from Jan 19, 2014

Conversation

daniel-beck
Copy link
Member

...name.

This change uses the top-most matching log recorder (based on name) to determine whether a log message should be added.

If both com (at INFO) and com.example (at WARNING) are defined for a specific log recorder, a log message in logger com.example.Foo will only be logged if it's WARNING or SEVERE, or the com logger is above the com.example logger in the loggers list.

This change will definitely impact existing configurations that start out with fairly restrictive log levels on e.g. com, to be more verbose with specific loggers later.

This PR is one of two proposed solutions to JENKINS-21386, the other being #1090.

@cloudbees-pull-request-builder

core » jenkins-core #51 SUCCESS
This pull request looks good

@kohsuke kohsuke merged commit bd6b999 into jenkinsci:master Jan 19, 2014
daniel-beck referenced this pull request Jan 19, 2014
Conflicts:
	core/src/main/java/hudson/logging/LogRecorder.java
	core/src/test/java/hudson/logging/LogRecorderTest.java
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants