| Jesse Glick - thanks for the prompt response. You are probably right. I'll do testing with different combinations of jdk-8 and without HTTPS today. It will take me a bit of time to come up with the smallest reproducible setup and test with jdk-8. server-*.pem is a self-signed cert with :
localhost
127.0.0.1
jenkins-server
google chrome likes it when imported (Mac/Linux) The client / agent are connecting using a different container over a bridge network. server:
# winstone args
--httpsPort=${HTTPS_PORT-8443} \
--httpsPrivateKey=/var/jenkins_home/tls/server-rsa.pem \
--httpsCertificate=/var/jenkins_home/tls/server-cert.pem} \
--extraLibFolder=/var/jenkins_home/extraLibs \
--accessLoggerClassName=winstone.accesslog.SimpleAccessLogger \
--simpleAccessLogger.format=combined \
--simpleAccessLogger.file=/var/jenkins_home/logs/access.log \
client:
java \
-Djavax.net.ssl.trustStore=/var/lib/jenkins/truststore.jks \
-Djavax.net.ssl.trustStorePassword=jenkins \
-Djava.util.logging.config.file=/var/lib/jenkins/debug-logging.properties \
-jar "../jenkins-cli.jar" \
-s "https://jenkins-server:8443" \
-webSocket \
-logger FINE \
-auth "$AGENT_AUTH" \
<args>
|
