• 1.554.1 (1.554.1/Dockerfile)
• 1.554.2 (1.554.2/Dockerfile)
• 1.554.3 (1.554.3/Dockerfile)
• 1.555 (1.555/Dockerfile)
• 1.556 (1.556/Dockerfile)
• 1.557 (1.557/Dockerfile)
• 1.558 (1.558/Dockerfile)
• 1.559 (1.559/Dockerfile)
• 1.560 (1.560/Dockerfile)
• 1.561 (1.561/Dockerfile)
• 1.562 (1.562/Dockerfile)
• 1.563 (1.563/Dockerfile)
• 1.564 (1.564/Dockerfile)
• 1.565.1 (1.565.1/Dockerfile)
• 1.565.2 (1.565.2/Dockerfile)
• 1.565.3 (1.565.3/Dockerfile)
• 1.565 (1.565/Dockerfile)
• 1.566 (1.566/Dockerfile)
• 1.567 (1.567/Dockerfile)
• 1.568 (1.568/Dockerfile)
• 1.569 (1.569/Dockerfile)
• 1.570 (1.570/Dockerfile)
• 1.571 (1.571/Dockerfile)
• 1.572 (1.572/Dockerfile)
• 1.573 (1.573/Dockerfile)
• 1.574 (1.574/Dockerfile)
• 1.575 (1.575/Dockerfile)
• 1.576 (1.576/Dockerfile)
• 1.577 (1.577/Dockerfile)
• 1.578 (1.578/Dockerfile)
• 1.579 (1.579/Dockerfile)
• 1.580.1 (1.580.1/Dockerfile)
• 1.580.2, latest (1.580.2/Dockerfile)
• 1.580 (1.580/Dockerfile)
• 1.581 (1.581/Dockerfile)
• 1.582 (1.582/Dockerfile)
• 1.583 (1.583/Dockerfile)
• 1.584 (1.584/Dockerfile)
• 1.585 (1.585/Dockerfile)
• 1.586 (1.586/Dockerfile)
• 1.587 (1.587/Dockerfile)
• 1.588 (1.588/Dockerfile)
• 1.589 (1.589/Dockerfile)
• 1.590 (1.590/Dockerfile)
• 1.591 (1.591/Dockerfile)
• 1.592 (1.592/Dockerfile)
• 1.593 (1.593/Dockerfile)
• 1.594 (1.594/Dockerfile)
• 1.595 (1.595/Dockerfile)
• 1.596, weekly (1.596/Dockerfile)

For more information about this image and its history, please see the relevant manifest file (library/jenkins) in the docker-library/official-images GitHub repo.

The Jenkins Continuous Integration and Delivery server.

This is a fully functional Jenkins server, based on the Long Term Support release http://jenkins-ci.org/.

docker run -p 8080:8080 jenkins

This will store the workspace in /var/jenkins_home. All Jenkins data lives in there - including plugins and configuration. You will probably want to make that a persistent volume:

docker run --name myjenkins -p 8080:8080 -v /var/jenkins_home jenkins

The volume for the "myjenkins" named container will then be persistent.

You can also bind mount in a volume from the host:

First, ensure that /your/home is accessible by the jenkins user in container (jenkins user - uid 102 normally - or use -u root), then:

docker run -p 8080:8080 -v /your/home:/var/jenkins_home jenkins

If you bind mount in a volume - you can simply back up that directory (which is jenkins_home) at any time.

If your volume is inside a container - you can use docker cp $ID:/var/jenkins_home command to extract the data.

You can run builds on the master (out of the box) buf if you want to attach build slave servers: make sure you map the port: -p 50000:50000 - which will be used when you connect a slave agent.

Here is an example docker container you can use as a build server with lots of good tools installed - which is well worth trying.

All the data needed is in the /var/jenkins_home directory - so depending on how you manage that - depends on how you upgrade. Generally - you can copy it out - and then "docker pull" the image again - and you will have the latest LTS - you can then start up with -v pointing to that data (/var/jenkins_home) and everything will be as you left it.

This image is officially supported on Docker version 1.5.0.

Support for older versions (down to 1.0) is provided on a best-effort basis.

If you have any problems with or questions about this image, please contact us through a GitHub issue.

You can also reach many of the official image maintainers via the #docker-library IRC channel on Freenode.

You are invited to contribute new features, fixes, or updates, large or small; we are always thrilled to receive pull requests, and do our best to process them as fast as we can.

Before you start to code, we recommend discussing your plans through a GitHub issue, especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give you feedback on your design, and help you find out if someone else is working on the same thing.