-
Notifications
You must be signed in to change notification settings - Fork 658
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(jenkins): Igor fails to start if only keystore is configured #856
fix(jenkins): Igor fails to start if only keystore is configured #856
Conversation
This configuration worked fine in okhttp2, but not in okhttp3. As a workaround, Igor will try to use the keystore as a truststore as well, and prints a warning in the log.
if (trustManagers == null) { | ||
log.warn("${host.name}: okhttp3 (unlike okhttp2) doesn't support configuring only a keystore without " + | ||
"a truststore. Please configure a truststore to get rid of this message. Trying to use the " + | ||
"keystore '${host.keyStore}' as a truststore as well. Your mileage may vary.") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, I'm not sure we want to be advising this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sketchy advise in logs, I'd get rid of that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh. I read the log backwards. Looks fine.
This configuration worked fine in okhttp2, but not in okhttp3.
As a workaround, Igor will try to use the keystore as a truststore as well, and prints a warning in the log.
"Bug" introduced in #834. Keystore support was added in #596.