Talk from the inaugural JHipster Melbourne Meetup (21/06/2017) about the various JHIpster generators available for CI/CD. Discusses Jenkins 2, Heroku, Gitlab and Rancher. Associated Repository: https://github.com/ggotti/jhipster-ci-cd-talk

1. Putting the FUN into
Functioning CI/CD
Gerard Gigliotti

2. Continuous Integration (CI) Definition
Continuous integration (CI) is the
practice of merging all developer working
copies to a shared mainline several
times a day. - Random Wikipedia Editor

3. Continuous Delivery (CD) Definition
Continuous Delivery is a software
development discipline where you build
software in such a way that the software
can be released to production at any
time. - Martin Fowler

4. So, how does
JHipster help?

5. Plethora of Generators
Continuous Integration
● Jenkins (1 + 2)
● Travis
● CircleCI
● GitLab CI
Deployment Options
● Cloud Foundry
● Heroku
● Kubernetes
● OpenShift
● Rancher
● AWS
● Boxfuse

6. Jenkins + Heroku

7. Why Heroku?
● Easy to deploy.
● Free: However, If you’re deploying an application with a database,
you’ll need to validate your Heroku Account with a Credit Card.
● First class support in JHipster.
● Sydney Private Space support announced this year.
● Why not Heroku?
○ Low enterprise Market penetration.
○ Not as portable as Docker.

8. Heroku Generator
● You need to deploy the JHipster Registry first; no Consul support.
● Setup the Heroku CLI.
● Then:
jhipster heroku
● Deploys your app straight away.

9. Why Jenkins?
● Jenkins 2.0. Not your father’s Jenkins.
● Pipeline as code. Groovy DSL.
● Great path to upgrade existing installs/migrate from Bamboo.
● Multiple stages.
● Option to perform build in Docker container.
● Can include Docker image generation.
● Why not Jenkins?
○ Plugin quality varies dramatically.
○ Maintenance headache.
○ Groovy?

10. Jenkins 2.0 Generator
Produces this beautiful thing
jhipster ci-cd

11. Tying it Together
● Heroku API Key is needed in Jenkins. Don’t copy it into the repo.
● Modify the “deployment” stage to use the Credentials Binding
Plugin:
withCredentials([string(credentialsId: 'HEROKU_API_KEY', variable: 'HEROKU_API_KEY')]) {
sh "./gradlew deployHeroku --no-daemon"
}
● That’s it.

12. Gitlab + Rancher

13. Why Gitlab?
● It does everything:
○ Source Control
○ Issues Tracking
○ Story Board
○ Build Pipeline
○ Docker Registry
● Open Source, fast paced release schedule.
● Built with Docker in mind.

14. Gitlab Generator
jhipster ci-cd
Produces this beautiful thing

15. Some Tiny Alterations
● Modified the gradle-package step:
gradle-repackage:
image: ggotti/jhipster-gitlab-java-docker-builder
stage: package
services:
- docker:dind
variables:
CONTAINER_BASE: lyon.gigliotti.com.au
CONTAINER_NAME: lyon.gigliotti.com.au/meetup_gateway
before_script:
- docker login -u admin -p $DOCKER_REPO_PWD $CONTAINER_BASE
script:
- ./gradlew -Pprod -x check -PnodeInstall --no-daemon bootRepackage buildDocker -x test -x check
- docker tag gateway $CONTAINER_NAME
- docker push $CONTAINER_NAME
● My custom Docker image is a frankenstein of the OpenJDK:8 image
with Docker installed.
● Allows Docker image to be built on Docker Runner.
Docker-in-Docker. See a comparison of runners here.

16. Why Rancher?
● Docker Container Management.
● Simplified mechanism for running Docker Containers in production.
● Great option for managing cloud and on-prem hosts.
● Can slot in alongside your existing Docker deployment processes. A
bit more visual.
● JHipster uses Docker extensively. Generate one image, use in dev to
production.
● Why not Rancher?
○ Not integrated out of the box with JHipster + Gitlab. The batteries are not included.
○ Generator is in Beta.
○ It’s not as cool as Kubernetes.

17. Rancher Generator
● jhipster rancher-compose

18. Gitlab Pipelines
Gitlab + Rancher Pipeline Palooza
Gateway Rancher
Rancher
Containers
Docker Registry
gateway image
config-side-kick image
Load Balancer
Gateway Application
Gateway MariaDB
JHipster Registry
Pulls gateway image +
config-side-kick
Gitlab
Trigger

19. An entirely new .gitlab-ci.yml

20. Gitlab Trigger
● Currently no way to easily invoke a pipeline from another repo.
Triggers are the workaround.

21. Seamlessly Deploy to Rancher*
*
most of the time

22. Source Repo
https://github.com/ggotti/jhipster-ci-cd-talk

23. Fin

24. PARIS
BORDEAUX
NANTES
WASHINGTON, DC
NEW-YORK
RICHMOND, VA
MARRAKECH
MELBOURNE
contact@ippon.fr
www.ippon.fr
www.ippon-hosting.com
www.ippon-digital.fr
@ippontech
01 46 12 48 48