| commit | 1ac0bcd299393e60158e3aafbc29f75b4e40e9d2 | [log] [tgz] |
|---|---|---|
| author | Vincent Dupain <vdupain@generali.com> | Mon Aug 18 15:06:43 2014 +0200 |
| committer | Vincent Dupain <vdupain@generali.com> | Mon Aug 18 15:06:43 2014 +0200 |
| tree | 9d90fc5dc397d49fa0c66652c839a29a3648e85c | |
| parent | a5bfd41e00d0df91a35dd6a252b8c4a831d00743 [diff] |
Adding url prefix
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.