Downloaded 12 times
Uploaded byShreyas Chaudhari
Jenkins : Pipeline As Code
The document outlines a presentation on Jenkins, focusing on its use in continuous integration and continuous delivery, as well as introducing various Jenkins project types, including freestyle and pipeline projects. It discusses the benefits of using Jenkins pipelines, such as their durability, versatility, and ease of integration with source control management (SCM). The presentation includes technical concepts, rules for engagement, and encourages audience participation while providing resources for further exploration.
Jenkins : Pipeline As Code
- 1. Jenkins : Pipelineas Code Shreyas & Inder vodQA, Pune 16th March 2019
- 2. Shreyas Chaudhari Quality Analystat ThoughtWorks, Inc About Me
- 3. Inder Pal Singh AboutMe Quality Analyst at ThoughtWorks, Inc
- 4. 4 Ground Rules ● Followthe speaker ● Don’t get deviated ● If you are stuck, call any of the volunteers ● We will share all the material with you, don’t bother about that ● Ask questions whenever you have - Don’t wait ● We will focus more on Action than on Philosophy
- 5. 5 Agenda ● Continuous Integration& Continuous Delivery ● What is Jenkins? Why Jenkins? ● Jenkins Project Types ● Freestyle Project ● Why Pipeline ● Pipeline Concepts ● Pipeline - Structured & Declarative ● Jenkins Job Builder ● Architecture, Automation Framework Architecture & CI Workflow ● References
- 6. 6 Continuous Delivery Continuous Integration ●Integrate code into a shared repository frequently ● Each check-in is verified by an automated build ● Can detect errors Early and Easily Continuous Deployment ● Ability to get changes into production or into the hands of users. ● Code always in deployable state
- 7. 7 Continuous Integration ● Ata minimum: ○ Gather latest source together ○ Compile ○ Execute tests ○ Verify success ● Can include other tasks such as: ○ Rebuild the database ○ Build release distribution ○ Run code analysis and coverage tools ○ Generate documentation
- 8. 8 Continuous Delivery VsContinuous Deployment
- 9.
- 10. 10 Jenkins ● Open Source ●Free ● Easily Configurable ● Rich Plugin Ecosystem ● Easy Support ● Fork of Hudson ● Configuration through - GUI and Console Commands
- 11. 11 Jenkins - ProjectTypes ● Freestyle Project ● Pipeline ● Multibranch Pipeline
- 12.
- 13. 13 What is Pipeline? Suiteof plugins Domain Specific Language Extensible set of tools Text File in SCM
- 14. 14 Why Pipeline? Code Implemented andChecked in SCM Durable Survive Jenkins Restarts Pausable Can Stop Or Wait For Human Approval Versatile Complex CD Requirements Extensible Easier to add Plugins in DSL
- 15. 15 Benefits of Pipeline Automaticallycreates a pipeline Code review / iteration on the pipeline Single source of truth
- 16. 16 Pipeline Commands Pipeline User definedmodel of CD pipeline Node Machine in Jenkins environment Stage Conceptually defined subsets of tasks Steps Granular task that tells Jenkins what to do
- 17. 17 Pipeline Types -Scripted Vs Declarative Scripted Pipeline ● Tremendous amount of Flexibility and Extensibility ● Groovy language has a limited learning curve ● Imperative Programming Declarative Pipeline ● Simpler and Opinionated syntax ● Limits user with strict and predefined structure ● Declarative Programming
- 18. 18 Pipeline Concepts -Scripted Vs Declarative
- 19.
- 20. 20 Jenkins Job Builder ●Configures Jenkins by taking Yaml or Json ● Yaml or Json are human readable ● Create Jenkins job xmls from yamls or jsons ● Uploads to Jenkins using HTTP Api ● Also has Template system
- 21. 21 How to createBuild Pipelines? JENKINS JOB BUILDER PIPELINE CODE TEMPLATES JOBS APP TEAM PET
- 22. 22 Avoid perils ofShared CI TOPOLOGY DATA PIPELINE CODE APP TEAM’S JOBS
- 23.
- 24.
- 25. THANK YOU For questionsor suggestions mailto: shreyasc@thoughtworks.com inderpal@thoughtworks.com