Re: [JNLP][Agent][Docker] connect an Agent to a Jenkins instance using self-signed certs

On Monday, April 13, 2020 at 11:02:12 PM UTC+5:30, Ivan Fernandez Calvo wrote: > > I make it with JCasC, basically is a Docker compose with Jenkins, > openSAML, and a SSH Build Agent, it is what I use to test issues see > https://github.com/kuisathaverat/jenkins-issues/tree/master/jobDSL > >

Re: [JNLP][Agent][Docker] connect an Agent to a Jenkins instance using self-signed certs

I make it with JCasC, basically is a Docker compose with Jenkins, openSAML, and a SSH Build Agent, it is what I use to test issues see https://github.com/kuisathaverat/jenkins-issues/tree/master/jobDSL You have a bunch of examples on the JCasC demo folder

Re: [JNLP][Agent][Docker] connect an Agent to a Jenkins instance using self-signed certs

On Saturday, April 11, 2020 at 5:43:28 PM UTC+5:30, Ivan Fernandez Calvo wrote: > > Hi, > > I have a Jenkins instance running (2.230, also I have tested LTS) on a > Docker container using only HTTPS with self-signed certificates, in the > same network I start an SSH Build Agent and a JNLP

Re: [JNLP][Agent][Docker] connect an Agent to a Jenkins instance using self-signed certs

Well, it was a stupid thing the URL that I pass to the Docker container is the JNLP agent URL ( https://jenkins:9443/computer/jnlp-agent/slave-agent.jnlp ), it should be the Jenkins URL (https://jenkins:9443 ), so that's my error.

[JNLP][Agent][Docker] connect an Agent to a Jenkins instance using self-signed certs

Hi, I have a Jenkins instance running (2.230, also I have tested LTS) on a Docker container using only HTTPS with self-signed certificates, in the same network I start an SSH Build Agent and a JNLP Agent, the SSH Build agent connects without issues, but the JNLP gives me an error I dunno what