Docker image for inbound Jenkins agents
This is an image for Jenkins agents using TCP or WebSockets to establish inbound connection to the Jenkins master. This agent is powered by the Jenkins Remoting library, which version is being taken from the base Docker Agent image.
See Jenkins Distributed builds for more info.
To run a Docker container
docker run --init jenkins/inbound-agent -url http://jenkins-server:port <secret> <agent name>
--init is necessary for correct subprocesses handling (zombie reaping)
docker run jenkins/inbound-agent:windowsservercore-1809 -Url http://jenkins-server:port -Secret <secret> -Name <agent name>
To run a Docker container with Work Directory
docker run --init jenkins/inbound-agent -url http://jenkins-server:port -workDir=/home/jenkins/agent <secret> <agent name>
docker run jenkins/inbound-agent:windowsservercore-1809 -Url http://jenkins-server:port -WorkDir=C:/Jenkins/agent -Secret <secret> -Name <agent name>
Optional environment variables:
JENKINS_URL: url for the Jenkins server, can be used as a replacement to
-urloption, or to set alternate jenkins URL
HOST:PORT) connect to this agent host and port instead of Jenkins server, assuming this one do route TCP traffic to Jenkins master. Useful when when Jenkins runs behind a load balancer, reverse proxy, etc.
JENKINS_SECRET: agent secret, if not set as an argument
JENKINS_AGENT_NAME: agent name, if not set as an argument
JENKINS_AGENT_WORKDIR: agent work directory, if not set by optional parameter
trueif the connection should be made via WebSocket rather than TCP
Enabled JNLP protocols
As of version 3.40-1 this image only supports the JNLP4-connect protocol. Earlier, long-unsupported protocols have been removed. As a result, Jenkins versions prior to 2.32 are no longer supported.