Jenkins Docker Plugin: Difference between revisions
Jump to navigation
Jump to search
Line 27: | Line 27: | ||
{{External|https://hub.docker.com/r/jenkins/jnlp-slave/}} | {{External|https://hub.docker.com/r/jenkins/jnlp-slave/}} | ||
The image comes with JDK. Jenkins master URL has to be reachable from the agent's container. The container will be configured automatically with the agent's name and secret. No special configuration of the container is needed. | |||
===jenkins/slave=== | |||
{{External|https://hub.docker.com/r/jenkins/slave/}} | |||
An "attached" agent. | |||
===jenkins/slave=== | ===jenkins/slave=== |
Revision as of 21:04, 23 April 2018
External
Internal
Overview
ID: docker-plugin
Concepts
Docker Agent
Jenkins can interact with agents executing as containers within a Docker instance. The agent containers must be based on one of the following base images:
jenkins/ssh-slave
The image comes with sshd and a JDK. The Jenkins master will use ssh to connect into the agent's sshd. A SSH key based on unique Jenkins master instance identity can be injected in container on startup, obviating the need for password.
jenkins/jnlp-slave
The image comes with JDK. Jenkins master URL has to be reachable from the agent's container. The container will be configured automatically with the agent's name and secret. No special configuration of the container is needed.
jenkins/slave
An "attached" agent.
jenkins/slave
Installation
Manually from the UI or:
/usr/local/bin/install-plugins.sh docker-plugin