Default INFO logging makes jenkins cli output messages that are then … #907
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.
…evaluated as non-valid json
Pull Request (PR) description
After upgrading or setting up new jenkins masters based on the new jenkins LTS release 2.164.1, we noticed the same issues as mentioned in an earlier opened issue. Jenkins client jar gives back some "INFO" level messages when starting and when puppet tries to use that output combined with the real json, it of course sees that the total result is not valid json.
This PR make sure that only warning or worse messages get outputted by the jenkins-client.jar for usage with the puppet provider.
This Pull Request (PR) fixes the following issues
Fixes #905