shazchaudhry / docker-jenkins

Customized image with docker and selected plugin pre-backed. This image makes use of docker secrets and runs in a swarm cluster

This image extends the latest version of Jenkins Continuous Integration and Delivery server. Additionally, it comes with the latest stable version of Docker engine and the following plugins are pre-installed:

• blueocean
• keycloak
• role-strategy

Create local environment

• Clone this repository: git clone https://github.com/shazChaudhry/docker-jenkins.git
• Change directory: cd docker-jenkins
• Run provided vagrantfile: vagrant up
• ssh to the vagrant box: vagrant ssh
• Change to synched folder: cd /vagrant

play-with-docker environment

• Navigate to http://play-with-docker.com/ and create docker swarm environment
• Clone this repository: git clone https://github.com/shazChaudhry/docker-jenkins.git && cd docker-jenkins

Instructions to run Jenkins

1. Execute this step if building the image from source. Otherwise skip to step 2 Use the following command to build the image from source:

    docker image build --no-cache \
    --tag shazchaudhry/docker-jenkins:latest \
    --build-arg GIT_COMMIT=$(git log -1 --format=%H) .

    Run this command to confirm git commit:-
    docker image inspect shazchaudhry/docker-jenkins:latest | jq '.[].ContainerConfig.Labels'

2. Use the following commands to run the image:

    echo "admin" | docker secret create jenkins-user -
    echo "admin" | docker secret create jenkins-pass -
    docker stack deploy --compose-file=docker-compose.yml jenkins
    docker stack services jenkins

Test

• If provided vagrantfile is being used, in your favorite web browser, navigate to http://node1/jenkins
  • username = admin
  • password = admin

Visualization

• docker stack deploy --compose-file=docker-compose.portainer.yml portainer Use Portainer agent setup to deploy inside a Swarm cluster
• Portainer is available at http://node1:9000. Portainer documentation is here on github

Clean up:

• vagrant destroy --force destroy all VMs that were created above

docker-jenkins's Issues

Use letsencrypt for the proxy

generate certificates using: https://github.com/n1b0r/docker-flow-proxy-letsencrypt

Upgrade compose version to 3.7 in docker-compose.portainer.yml

Check docker engine release physically for D4AWS first by launching a swarm cluster. If it happens to be 18.06.0+ then upgrade the compose version to v3.7 in docker-compose.portainer.yml (version information provided on https://docs.docker.com/docker-for-aws/release-notes/#stable-channel may not be correct)

See compose versioning page for the compatibility matrix: https://docs.docker.com/compose/compose-file/compose-versioning/