[JENKINS-73402] Load LogManager recorder afetr CasC loading #556
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Was probably introduced by #338.
Propose to load the recorders after CasC init (see https://github.com/jenkinsci/configuration-as-code-plugin/blob/1810.v9b_c30a_249a_4c/plugin/src/main/java/io/jenkins/plugins/casc/ConfigurationAsCode.java#L337).
I thought about just always targeting the reference
Jenkins.get().getLog().getRecorders()
from CustomHandler#publish but wonder if that would be overkill ? We go through this for every log record.. cc @jglick I wonder WDYT about this ?Testing done
$JENKINS_HOME/logs/custom/reactor.log
existsSubmitter checklist