-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
The head at the time of analysis was: c11a7c7
In `GithubServerContainer.java` there are two catch blocks with `INFO` logs:
- https://github.com/jenkinsci/blueocean-plugin/blob/b4c2050d3ac0a3135a96dcb7beccb1d88c9dcaa6/blueocean-github-pipeline/src/main/java/io/jenkins/blueocean/blueocean_github_pipeline/GithubServerContainer.java#L105-L107
- https://github.com/jenkinsci/blueocean-plugin/blob/b4c2050d3ac0a3135a96dcb7beccb1d88c9dcaa6/blueocean-github-pipeline/src/main/java/io/jenkins/blueocean/blueocean_github_pipeline/GithubServerContainer.java#L112-L116
Contrast this with other catch blocks that have a `WARNING` level:
- https://github.com/jenkinsci/blueocean-plugin/blob/b4c2050d3ac0a3135a96dcb7beccb1d88c9dcaa6/blueocean-commons/src/main/java/io/jenkins/blueocean/commons/stapler/export/Property.java#L253-L257
- https://github.com/jenkinsci/blueocean-plugin/blob/b4c2050d3ac0a3135a96dcb7beccb1d88c9dcaa6/blueocean-commons/src/main/java/io/jenkins/blueocean/commons/stapler/export/Property.java#L269-L273
It may be the case that `INFO` is not the appropriate level for these exceptions.