Skip to content

Conversation

@jimklimov
Copy link
Contributor

As @basil asked, here is another presumably not problematic subset of #59 that adds logging instrumentation in the code going through build parameter filtering. Due to the split of PRs, there may be a little formatting conflict vs. #75 that is another part of that original wad of code, and vs. subsequent PR with actual attempt at the fix.

@jimklimov
Copy link
Contributor Author

Updated for minor conflicts after #75 was merged

@basil
Copy link
Member

basil commented Sep 8, 2021

@jimklimov Is there still a strong motivation to finish and merge this PR? I'm not sure if this is still useful or if it has outlived its purpose after it was used to successfully debug previous issues.

If it is still needed, I'm concerned about the cost of the string concatenation for all the fine log statements. This is a hot code path in Jenkins, so any extra overhead here is a bit of a risk. The traditional best practice for this in Java is to guard such string concatenation with e.g. if (logger.isDebugEnabled()) {, but newer versions of Java allow for lazy computation of the string by using lambdas. This article explains both approaches.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants