Jenkins 2022 and beyond

Is the Butler Still Young? Maybe not but it is still one of the most popular automation tools. Jenkins in 2022 is not Jenkins in 2012. It keeps evolving to address demands from its users and contributors: pipeline as code, configuration as code, better support for cloud environments, UX, etc. We are looking forward to the next major iteration in Jenkins evolution. So what’s next for it? I will focus on the current challenges for Jenkins. What does need to change in the project and the community to keep it relevant? We will talk about revitalizing the community and attracting new company contributors, consolidating user experiences, and reusing experiences of BlueOcean and Jenkins X? We will also talk about interoperability with other projects, making Tekton a first class citizen Pipeline engine, and making Jenkins available everywhere regardless of CI/CD system you actually use.

Transcript

1. Jenkins 2022 and beyond Oleg Nenashev, Dynatrace 1
2. > whoami @oleg_nenashev oleg-nenashev 2
3. Outline Slides are public! Target audience: Jenkins users and contributors Plan: History dive My vision for Jenkins What’s next for Jenkins? Disclaimer: This presentation represent the opinions of the presenter and do not necessarily represent the official position of the Jenkins community or Dynatrace 3
4. Taking a break in Jenkins • On sabbatical in the community • It’s not due to leaving CloudBees • Reasons: personal events, ongoing war • I participate in governance and GSoC • I will be back! CDF Statement We stand with the people of Ukraine. Please assist humanitarian efforts for the Ukrainian people and those affected by the military invasion of Ukraine by supporting international aid organizations, including UNICEF. 4
5. > whoami --jenkins @oleg_nenashev oleg-nenashev 5
6. History Dive 6
7. Jenkins Is The Way video, sponsored by CloudBees: https://youtu.be/fgd1bBlQXBE 7
8. Let’s skip 15 years… // see the presentations by Kohsuke Kawaguchi 8
9. Who is Mr. Jenkins? Automation server/framework Open-source More than 1800 plugins Big community Commercial support is available 9
10. Jenkins’ recipe of success • Extensible • General-purpose • Community 10
11. Jenkins community • Open governance • Jenkins evolution is defined by contributors • Open to any individual and company contributor • Maintainers have full freedom in their plugins 11
12. It works well! 12
13. != 13
14. Modern Jenkins • • • • • Pipeline-as-Code Configuration-as-Code New plugins and integrations Modern packaging Distributions for public clouds 14
15. Project keeps growing https://jenkins.devstats.cd.foundation/d/15/new-prs-in-repository-groups?orgId=1&var-period=q &var-repogroup_name=All&from=now-10y&to=now 15
17. Obstacles we hit • Isolated sub-communities • Lack of transparency • Perceived lack of focus • Hard to get multiple contributors behind big initiatives • Hard to join initiatives 17
18. Jenkins community consolidation • 2011 - Open Governance, Governance Meetings • 2015 - Teams, Jenkins Officers, sub-projects • 2017 - Jenkins Enhancement Proposals • 2018 - Special interest groups (SIGs) • 2019 - Governance Board elections • 2019 - CDF Membership, founding project • 2020 - Graduation at CDF • 2020 - Public roadmap 18
19. Public Roadmap RELEASED PREVIEW CURRENT NEAR-TERM FUTURE Published on July 15, 2020 Open process (JEP-14) A bit outdated :( Target audience: • Jenkins users • Contributors • Adopters and vendors jenkins.io/project/roadmap 19
20. Roadmap Concepts • Community-driven • All initiatives: features, docs, infrastructure, community • Open and transparent process • Open data • No commitment on dates and delivery at all github.com/jenkinsci/jep/tree/master/jep/14 20
21. Beyond 2015 Obstacles for Jenkins 21
22. Slides: https://docs.google.com/presentation/d/1FuMR2 ZxO-S6HtcIUeekym0MZIp9rn-b5ql6sYBMSgK4/ edit?usp=sharing 22
23. Generations of CI/CD Tools (Oleg’s IMHO) I CRON II III ... 23
24. Generation III. New demands Generation III evolves … but not fast enough for early adopters Shift left 24
25. Evolution of generation III III R.I.P. Evolution ??? IV 25
26. Image: dronetrest.com/t/diy-self-build-drones-or-ready-to-fly-rtf-drones/1414 26
27. Expectation 27
28. Expectation Reality 28
29. CI/CD System from Jenkins Samples Demos Configs Ba ck en d Plugins Система Infrastruc ture Infrastruc ture Infrastruc ture Docs 29
31. frameworks Samples Demos Plugins Configs Система ? Ba ck en d without proper maintenance Infrastructure Infrastructure Infrastructure Docs 31
32. It is hard to maintain Jenkins • Fine-tuning is needed • Maintenance is needed • Expertise is needed 32
33. Learning Curve Advanced features, Custom setups Plugins Scripts, CRON 33
34. >10 years of compatibility Hudson 2 plugins still work! BUT: • Architecture issues • Old libraries • Obsolete UI • Plugin compatibility issues • Regular Security-updates 34
35. Scalability Jenkins controllers handle the most of the workload Jobs run on controllers, agents just execute subtasks Controller 35
36. UI/UX is still perceived to be old but it’s not anymore! 36
37. Classic Approaches are still there Approach: Using “classic” Job types: Freestyle, Matrix, JobDSL, … Keywords: • Script steps to run the logic • Custom Tools Plugin to manage tools • Throttle Concurrent Builds and Lockable Resources to dispatch access to hardware • Naginator Plugin to restart builds on-demand • Parameterized Trigger / Copy artifacts to parallelize tests and to collect results 37
38. What’s next for Jenkins? 38
40. Shifting Gears: Making Changes Aug 31, 2018 – Kohsuke Kawaguchi, “Jenkins: Shifting Gears” https://jenkins.io/blog/2018/08/31/shifting-gears/ 40
41. https://docs.google.com/doc ument/d/1B70bAPlinLPOQ7 YGZCbg-3kN2IyIYlc9laubO MI-kMA/edit?usp=sharing 41
42. Jenkins = Community + Project Community > Project 42
43. Jenkins as community • Making Jenkins the best place to contribute • Focus on future. Jenkins is here to stay • Open, not just open source • Vendor neutral. More vendors involved • No vendor lock-in in open source components 43
44. Jenkins as project 1. Jenkins Anywhere 2. Cloud-Friendly Architecture 3. UX is a priority 4. Jenkins as a Framework 5. Compatibility in Mind 6. Security in mind 44
45. User Experience and User Interface UI/UX Revamp: Look & Feel, Themes, Accessibility User documentation and guidelines (?) Better Pipeline browsing jenkins.io/sigs/ux 45
46. Continued evolution – Jenkins Pipeline engine • Pipeline as YAML • Jenkins Templating Engine • IDE integrations • Documentation Improvements jenkins.io/sigs/pipeline-authoring 46
47. Jenkins on Classic Platforms 47
48. Kubernetes We have to be there! 48
49. … and Cloud Platforms Kubernetes, Kubernetes, Kubernetes Operators and Helm charts Jenkinsfile Runner – Portable Pipeline engine / FaaS Support for more Pipeline engines, esp. Tekton 49
50. Jenkins Interoperability Wishlist • Further adoption of OpenTelemetry • Adopt CDEvents for events and triggers • Tekton as a first class citizen Pipeline Engine • More automation, less orchestration. Integrate with tools like Spinnaker, Jenkins X or Keptn 50
52. != 52
53. Takeaways Jenkins in 2020 != Jenkins in 2012 Jenkins keeps changing Public roadmap Many projects are underway It worth exploring! 53
54. It’s [always] a great time to contribute ;) https://jenkins.io/participate 54
55. It’s great time to contribute! https://jenkins.io/participate 55
56. Contributing is not only about code Join special interest groups (SIGs) Let us know about your pain-points Share your stories and experiences jenkins.io/blog and other blogs community.jenkins.io Meetups Jenkins DEV list Jenkins needs you! 56
57. Join the Jenkins Contributor Summit! Thursday, June 9 (9:00 am – 5:00 pm CDT) Location: JW Marriott Austin. 57
58. QUESTIONS? Contacts: E-mail: onenashev@cloudbees.com GitHub: oleg-nenashev Twitter: @oleg_nenashev 58