Continuous Delivery Pipeline

This clusters is configured to use a significant amount of resources. Current set up allocats 6 CPU and 6 GB of memory.

Prerequisites

• Vagrant + VirtualBox

Given:

$ git clone https://github.com/mjvdende/continuous-delivery-pipeline.git 
$ cd continuous-delivery-pipeline

When:

$ vagrant up

Then:

start building!

It can take a while before services are started because docker is downloading images from the docker hub. Therefor you can follow the progress of services booting when logging on to a core, for example core-02.

$ vagrant ssh core-02
$ journalctl -u jenkins.service -f

Services Provided

Once a sevice is started below links will point to your local instance of the running service.

core-01

• docker.service
• docker-registry.service - URL: Docker Registry
• docker-registry-web.service - URL: Docker Registry Web
• gitbucket.service - URL: GitBucket (login:root-root)

core-02

• docker.service
• jenkins.service - URL: Jenkins
• xldeploy.service - URL: XL Deploy
• artifactory.service - URL: Artifactory

core-03

• docker.service
• xlvtestiew.service - URL: XL Test View
• sonarqube.service - URL: SonarQube
• tomcat.service - URL: Tomcat

Config

Cloud-Config

To start our cluster, we need to provide some config parameters in cloud-config format via the *.user-data file and set the number of machines in the cluster in config.rb. For each core a user-data file exists. Our cluster will use an etcd discovery URL to bootstrap the cluster of machines and elect an initial etcd leader. Be sure to replace with your own URL from https://discovery.etcd.io/new in each *.user-data file.

coreos:
    etcd2:
        # generate a new token for each unique cluster from https://discovery.etcd.io/new?size=3
        # specify the initial size of your cluster with ?size=X
        # WARNING: replace each time you 'vagrant destroy'
        discovery: https://discovery.etcd.io/<token>

More about using cloud-config

Add a Service

You can add a serivce yourself to one of the *.user-data config files. Have a look at already defined services for examples.

- name: xldeploy.service
  command: start
  enable: true
  content: |
    [Unit]
    Description=XL Deploy
    After=docker.service
    Requires=docker.service

    [Service]
    TimeoutStartSec=0
    ExecStartPre=-/usr/bin/docker kill xldeploy
    ExecStartPre=-/usr/bin/docker rm xldeploy
    ExecStart=/usr/bin/docker run \
                     -p 4516:4516 \
                     --name="xldeploy" \
                     mjvdende/docker-xldeploy
    ExecStop=/usr/bin/docker stop xldeploy

To apply changes to *.user-data reload vagrant provisioning:

vagrant reload --provision

Todo

• jenkins install plugins git, maven release, sonarqube and xldeploy
• add petclinic jenkins job
• sonarqube build breaker plugin
• automatically replace token in *.user-data file