Have you ever looked for a platform to define builds and deployment pipelines with code written in a real programming language and stored inside version control? The 2016 major version of Jenkins introduced Pipeline as Code for this reason, instantly setting a standard for its huge community of users and plugins.
This workshop will put your hands on:
- building delivery pipelines which test a project in isolation, in integration environments and finally deploy it to production
- build all the pull requests in an organization to give timely feedback to developers
- make use of shared resources such as virtual machines, without failing because of race conditions or conflicting builds
- turn off unused virtual machines for costs saving
- remove duplication from pipelines by extracting libraries of steps
- automatically open pull requests proposing changes, such as the update of libraries