blacklabelops-legacy / jenkins Goto Github PK

Container should support setting plugins in txt-file analogous to official Jenkins: https://hub.docker.com/_/jenkins/

• Implementation of entryscript and Dockerfile logic.
• Manual and examples.

We had a need to install specific version of plugins.
We followed the documentation and attempted to stand up a new jenkins using this command:

docker run --name jenkins -e "JENKINS_PLUGINS=gitlab-plugin hipchat:2.1.0 swarm" -p 8090:8080 blacklabelops/jenkins --debug=9

Jenkins came up but when I went to Jenkins UI, went to manage plugins, installed plugin I did not see any plugins installed.

I assumed that adding :version number of the plugin was the problem so I ran

docker run --name jenkins -e "JENKINS_PLUGINS=gitlab-plugin hipchat swarm" -p 8090:8080 blacklabelops/jenkins --debug=9

Even after running this command I do not see any plugins installed.

Finally I ran this command:

docker run --name jenkins -p 8090:8080 blacklabelops/jenkins --debug=9

Even in this case I don't see any plugins installed.

Can you let us know how we can specify a list of plugins and their version via command line?

Thanks

Container needs a cli-mode:

• Cli must be extracted from war and laid inside a specific directory in Dockerfile
• Cli must be available in PATH
• Cli must be easily invokable through simple alias (e.b. jenkins-cli args).
• Cli must be configurable to specific server through env variable
• Cli must be executable with default target the local server.
• Cli must be executable with a linked container

Several sections inside the manual are out of date since Jenkins 2.0 or Docker 1.x.

The latest image has all the functionality from the pre-image so manual only needs to be adjusted.

I've tried building my app and running docker containers from a jenkins install from docker before and ran into a few problems. Have any thought been put into your jenkins build?

Otherwise all jobs will have access to it. So you need to add

unset JENKINS_ADMIN_USER
unset JENKINS_ADMIN_PASSWORD

when you don't need them any more. Unless I am missing something....

Thanks for the project, btw.!

Currently each release must be done manually.

All dependencies must be fixed throughout the project. (Container, installed software etc.)

Possible solution: Bash Release script for fixing versions.

Note: Also the volume must be tagged, in order to allow concurrent jenkins instances.

The current Nginx example does not work with the latest Jenkins under http.

The https settings seems to be working fine.

Still trying to figure out a working example with Nginx, Jenkins and http.

Hi guys,

I'm kind of new into docker and especially data only containers. I noticed that if I ran your docker-compose example I noticed that the data container is not mounted. I kind of think is because the compose rebuilds the container every time and not in the right order. Any idea what's happening ?

Backup and restore only works for fixed versions.

If you restore from a different version of jenkins, then jenkins overwrites the whole folder, deleting restored files. (Note: Happens on container restart)

Possible solution: Installing from rpm, this way possibly the home folder does not contain binaries. This is the case with current installing from war file.

Alternative solution: New script for only backup and restore of configurations.

I got this far:

• log into master via https (http if you didn't specify the keystore info) at port 8090
• use the initial key found in your server log to create an admin user
• create a swarm slave user and password
• edit your jenkins-slave.env file (SWARM_JENKINS_USER and SWARM_JENKINS_PASSWORD) to use the user/password for the swarm slave user you just created; leave SWARM_MASTER_URL blank so that the slaves use autodiscovery to find the master via UDP
• ctrl-c docker to stop it and do "docker-compose up" to restart it

but then the logs keep saying:

slave_1    | INFO: Retrying request
slave_1    | Aug 01, 2016 2:28:51 PM org.apache.commons.httpclient.HttpMethodDirector executeWithRetry
slave_1    | INFO: I/O exception (org.apache.commons.httpclient.NoHttpResponseException) caught when processing request: The server jenkins failed to respond
slave_1    | Aug 01, 2016 2:28:51 PM org.apache.commons.httpclient.HttpMethodDirector executeWithRetry
slave_1    | INFO: Retrying request
slave_1    | org.apache.commons.httpclient.NoHttpResponseException: The server jenkins failed to respond
slave_1    |    at org.apache.commons.httpclient.HttpMethodBase.readStatusLine(HttpMethodBase.java:1976)

but at least they don't say this any more if you didn't put that info in:
slave_1 | WARNING: Required credentials not available for BASIC <any realm>@jenkins:8080