Skip to content
New issue

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

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

Already on GitHub? # to your account

Default INFO logging makes jenkins cli output messages that are then … #907

Merged
merged 2 commits into from
Mar 27, 2019

Conversation

jhooyberghs
Copy link
Contributor

…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

@jhooyberghs jhooyberghs force-pushed the bugfix/jenkins_lts_cli branch from 6b7fd0b to 2e00e38 Compare March 25, 2019 13:39
Copy link
Contributor

@vStone vStone left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tests need fixing

@binford2k binford2k merged commit eb03118 into voxpupuli:master Mar 27, 2019
@bastelfreak bastelfreak added the bug Something isn't working label Mar 27, 2019
@TomRitserveldt TomRitserveldt deleted the bugfix/jenkins_lts_cli branch July 7, 2020 08:18
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

jenkins cli broken with latest LTS 2.164.1 ?
4 participants