Pipeline as code using Jenkins -Ministry of Testing
- 1. Pipeline as Code using Jenkins Introduction to Jenkins Pipeline in the QE workflow Anisha Narang Swapnil Jadhav Principal Software Quality Engineer | Red Hat QE Lead | Red Hat
- 2. Agenda: ● Introduction to Jenkins pipelines ● Pipeline Concepts and Syntax ● Making pipelines part of your codebase. ● Demo ● QnA
- 3. Challenges with Test Automation & CI/CDs ● Frequent releases demand robust regression suite ● Difficulties in managing complexities in Freestyle jobs ● Integration with Dev team’s deployment pipelines ● Migration of QA Jenkins VM ● In-ability to stop/pause jenkins job for user input.
- 4. What is Jenkins Pipeline? In Jenkins, a pipeline is a collection of events or jobs which are interlinked with one another in a sequence. It is a combination of plugins that support the integration and implementation of continuous delivery pipelines using Jenkins.
- 5. Why Jenkins Pipeline ● Jenkins file could be stored in SCM ● Single source of pipeline helps multiple users to contribute ● Audit Trail ● Pause/Start Pipeline for user’s inputs ● Easy to accommodate Complex Pipelines using loop, forks ● Easy job restoration during Jenkins Migration ● Resilient for unplanned restarts
- 6. Pipeline Concepts Pipeline as Code via the Pipeline specific DSL syntax. Jenkinsfile Definition of Jenkins pipeline in a text file. ● Pipeline ○ A Pipeline is a user-defined model of a CD pipeline; a Pipeline’s code defines your entire build process. ● Node ○ A node is a machine which is part of the Jenkins environment and is capable of executing a Pipeline. ● Stage ○ A stage block defines a conceptually distinct subset of tasks performed through the entire Pipeline (e.g. "Build", "Test" and "Deploy" stages) ● Step ○ A single task. Fundamentally, a step tells Jenkins what to do at a particular point in time (or "step" in the process)
- 7. Pipeline Syntax ● Declarative ● Scripted A Jenkinsfile can be written using two types of syntax:
- 9. Declarative Pipeline for Tests
- 10. Demo ● Getting started with Pipelines ○ Using the Web UI to write Pipeline ○ Configuring Selenium Java repo ○ Publish TestNG reports ● Configuring your jenkins job for API tests with Jenkinsfile ○ Parameterize the job ○ Add stages ○ Publish reports ○ Trigger emails.
- 11. References: - Getting started with Jenkins Pipeline -> https://www.jenkins.io/doc/book/pipeline/ Demo references: - Selenium java repo -> https://github.com/the-test-trove/Selenium-testNg-Maven - Configuring Jenkins job using Maven -> https://github.com/the-test-trove/Selenium- testNg-Maven/blob/main/jenkins_config/Jenkinsfile - API tests using lcc -> https://github.com/the-test-trove/api-tests-lcc - Jenkinsfile -> https://github.com/the-test-trove/api-tests- lcc/blob/master/jenkins_config/Jenkinsfile