There are a lot of books and publications about the continuous integration in the world. But in my experience it’s difficult to find information about how to open quality gates between automated tests and to continuous integration practice to in your current project. After reading several articles and even a couple of books you will understand how to work with it. But what next? I will share with you practical tips and tricks on how to lift iron curtain to your automated tests before a continuous quality practice today. It is for this reason why I am pleased to share with you my acquired experience in my presentation.
6. CI 101
It was first named and proposed by Grady Booch in 1991
7. CI 101
"At regular intervals, the process of
"continuous integration" yields
executable releases that grow in
functionality at every release. ... It is
through these milestones that
management can measure progress
and quality, and hence anticipate,
identify, and then actively attach risks
on an ongoing basis." --
12. Tip: use plugins.txt
cat Dockerfile
FROM jenkins
COPY plugins.txt /usr/share/jenkins/ref/
RUN /usr/local/bin/plugins.sh /usr/share/
jenkins/ref/plugins.txt
20. 2. What can you do with
Jenkins REST API?
• retrieve information from Jenkins for
programmatic consumption.
• trigger a new build
• create/copy jobs