Community
Participate
Working Groups
From: https://wiki.jenkins-ci.org/display/JENKINS/Docker+Plugin Background The aim of the docker plugin is to be able to use a docker host to dynamically provision a slave, run a single build, then tear-down that slave. Optionally, the container can be committed, so that (for example) manual QA could be performed by the container being imported into a local docker provider, and run from there. Internal ALM-DCS team requests that the JENKINS docker plugin be ported to Hudson to be used by teams primarily to reduce slave configuration and isolation.
There are three Jenkins docker-related plugins. 1. Configure slave using docker. https://wiki.jenkins-ci.org/display/JENKINS/Docker+Plugin 2. Use docker commands in build step. https://wiki.jenkins-ci.org/display/JENKINS/Docker+build+step+plugin 3. Build projects with a Dockerfile, and publish the resultant tagged image (repo) to the docker registry https://wiki.jenkins-ci.org/display/JENKINS/Docker+build+publish+Plugin There may be some overlap between 2 and 3?
*** Bug 457561 has been marked as a duplicate of this bug. ***
