Jenkins has been the preferred tool for continuous integration and deployment for many years already due to it's smooth user experience, easy configuration, abundance of available plugins and integrations. During the talk we will tell about best practices on using Jenkins together with Cloud Foundry installations, accelerating cloud-native application delivery and packaging using combination of Docker and Jenkins and thoughtful configuration of CI/CD pipelines and keeping apps up-to-date on all CF environments.

1. Andrei Krasnitski
Cloud Foundry Engineer
ALTOROS
@altoros
Continuous Integration and
Deployment with Jenkins for
PCF
@infra-red

2. 2
ABOUT JENKINS
An extensible automation server built on
the JVM with hundreds of plugin to support
nearly every continuous integration,
delivery and deployment pipeline
imaginable

3. 3
ABOUT ME
• Cloud Foundry Engineer at Altoros
Andrei Krasnitski
• Long time Jenkins user and community
member
• Contributor on various open-source
projects @infra-red
@andreikrasnitski
• Maintainer of the Log Search project

4. 4
WHY JENKINS?
• Easy setup Procedure
• Cross system support
• Answers to most of the questions are available on the WEB
• Extensive Documentation and Tutorials
• Distributed builds
• Full Transparency and Total Control

5. 5
LEARNING CURVE
Scripts,
Jenkins CRON with UI
Automation
flows based
on plugins
Custom plugins,
Advanced
features

6. 6
PIPELINE AS CODE
DESCRIBING JENKINS JOBS VIA CODE

7. 7
BENEFITS?
• CI pipelines + project source code are in a one place
• Configuration change tracking
• Built-in global library to share scripts, functions,
variables across jobs
• Extend the DSL with your own
steps

8. 8
PIPELINE SAMPLE
• Syntax: Groovy-based DSL
• Store job description on SCM, e.g. jenkinsfile in the repo’s root
• https://tiny.cc/jenkins-pipeline

9. 9
SNIPPET GENERATOR
• First steps are
always the hardest
• Create your code
for individual steps
• Discover all the
steps provided by
plugin

10. 10
PIPELINE EDITOR
• Edit the Jenkinsfile
for a specific branch
directly from the
Web user interface
using the Visual
Pipeline Editor

11. 11
TOOLS
• Blue Ocean editor
• Command-line pipeline linter
• Jenkins Pipeline Unit Testing Framework
• ”Replay” function

12. 12
MULTIBRANCH WORKFLOW
• Job configurations contain only the reference to the
SCM
• Jenkins takes pipeline from jenkinsfile in SCM
• Pull-request builds
• Jenkins creates separate subtasks for branches,
builds and report results separately
• Organization Folders

13. 13
BUILD ENVIRONMENT
JENKINS WORKERS

14. 14
CONTAINER RUNTIME
Docker
Kubernetes
Apache Mesos
Docker is an open platform for developers and sysadmins to build, ship, and run distributed
applications, whether on laptops, data center VMs, or the cloud.
Kubernetes is an open-source system for automating deployment, scaling, and management of
containerized applications.
Apache Mesos is an open-source project to manage computer clusters.

15. 15
BENEFITS?
• No need for manual worker nodes
management
• All builds run in stateless infrastructure
• Restriction of services
• Isolation of resources

16. 16
DOCKER SLAVES
• No need to install software on Jenkins nodes
• Use multiple versions of the same tool
• Possibility to use existing containers based on Dockerfile
content

17. 17
ARCHITECTURE DIAGRAM
Jenkins Server
Docker Swarm

18. 18
SUMMARY
• Finally nice pipelines!
• The way to go with Jenkins
• Many of Jenkins plugins already compatible
• Pipeline as code!
• Versioned
• Code sharing
• New UI stuff is still broken
• Endless possibilities – can be complex and
painful

19. altoros.com
blog.altoros.com
19
@altoros
Thank you!
@infra-red