Jenkins Automation

By: Toni Van de Voorde

When you want to guarantee code quality, do continuous deployments or any other automation you will need a good continuous integration server.

While there are many great (hosted) solutions like TravisCi, CircleCi, etc … when it comes to **full control** or the need for private hosting, **Jenkins** is the right candidate. However, Jenkins could be known to be hard to learn and to configure. But what if you could automate all that complexity via some **easy scripting**? We are developers after all ;).

This talk will give you an introduction on how to automate the setup and the configuration of your CI whether you are still using the old fashion way (freestyle jobs) or the newer recommended way (Pipelines).

Some examples that will be covered:

– Auto setup jenkins with plugins, credentials, …
– Generate jobs per branch fetched directly for your VCS (Bitbucket, Github, …) (the old fashion way)
– Arrange your jobs in folders
– Make reusable DSL functions
– Using conditionals (e.g. master => should deploy if build successful)
– generate (multi branch) pipeline jobs with, optionally, fully integration with Bitbucket or Github