Availability of Pipeline as Code significantly changed approaches to automation in Jenkins, especially in case of parallelized builds and tests. Now it’s possible to build a custom test framework and provide it to automation engineers as a set of libraries.
We'll show you how to build Pipeline libraries for QA tasks and how to migrate existing projects to a new platform. We will integrate Docker, Maven, JUnit, FindBugs, Coverity into our framework and then implement parallelization of tests and others stages. Then we will talk about common obstacles and the best-known development, testing and maintenance approaches to such frameworks.
Engineer at CloudBees, core team member in the Jenkins project. Since 2008 works in the areas of automation, infrastructures, and frameworks for mixed software-hardware projects, with the help of Jenkins and dozens of other tools. Oleg writes code, maintains Jenkins core and plugins, and organizes meetups and other community events.