Current state of Jenkins

May 4, 20115 likes2,873 views

The document summarizes updates to the Jenkins project since its split from the Hudson project in 2011. It discusses the interim governance board, increased development activity and contributions from the community, initiatives to improve plugin development and testing, and plans for a stable but older release line and logo contest. The project is thriving with more users, developers, and formal governance processes since the split from Hudson.

DivorceInfra issues in java.net led to the question over the control by Oracle (Nov 2010)Trademark was used as a weaponLed to discussion with Oracle offline to transfer the trademark custody to 3rd party foundationNegotiation failed. Vote proposed to rename Hudson to Jenkins (Jan 2011)Subsequently approved by 214-to-14

Jenkins Project Since Thenhttp://jenkins-ci.org/3 people interim governance boardMyselfAndrew Bayer from ClouderaDean Yu from YahooIn process of …Registering trademarkSeeking an umbrella organization for holding assets, CLA, etc.

Development in Jenkins ProjectMost Hudson developers moved to Jenkins733 commits since the divorce (vs 172)42% by community (vs 1%)By 48 people (vs 7)More contributions after divorce170 pull requests (vs 20)11.3 change log items per release (vs 6.7 before)94 publicized committers on GitHub (vs 4)496 repositories (vs 1)

Development in Jenkins ProjectPlugin development moved to JenkinsShowing # of commits in Hudson pluginsOf 25 top plugins21 moved to Jenkins4 had no commits40 new plugins since the split (vs 1)

Delivering what users needIterative, compatible improvements over the codebaseChanges that actually deliver values to usersJust like we’ve been doing all alongBugs/RFEs are getting delivered282 tickets fixed (vs 68)514 tickets created (vs 129)

Users are followingPublic Hudson sites moving to JenkinsApache, JRuby, NASA, Nuxeo, Scala, PiWiki, CreativeCommons, OpenIndiana, …Users list traffic1280 e-mails (vs 259)Downloads are healthy8132 war, 2733 deb, 1237 rpm, 1320 zip (per week)OS Distributions are switchingUbuntu, FreeBSD, OpenBSD

New InitiativesBi-weekly governance meetingHeld on IRC, open to everyoneDiscuss project issues and ideasMinutes open to anyone: http://meetings.jenkins-ci.org/Turns out very useful in …Getting fresh people into projectCreating stronger bonds among developers

“Stable But Older” Release LineMain release lineThe main release line continues as isEach releases goes through all our automated testsFork a maintenance branch every 3 months from a releaseOnly proven backported fixes from mainlineMonthly releaseHopefully 1.400.1 in May

Goal of “Stable But Older” Release LineHelp those who value stability more than new featuresSlower release cycles, more conservative changesProvide focal point for people doing their own QAOften a team in large company does this

Plugin compatibility testingFrederic Camblor is driving this effortRerun plugin tests against the latest version of JenkinsShould help us catch regressions earlier

Plugins in JRubyCharles Lowell is driving this effortJenkins used more and more in languages like Ruby, PHP, PythonThose users would like to write plugins in their languages, not in JavaHopefully attract new wave of plugin developers

My Focus in CoreServe plugin developers technicallyMore extension pointsBetter cross-referencing existing pluginsTechnologies to simplify their codeServe plugin developers sociallyHackathons, documentationRestore infrastructure support

My Focus in CoreContinue housekeeping workImproved modularityBug fixes, better error diagnostics, smoothing out rough edgesBetter native packagingPush features along development themesBut do so by writing plugins

ConclusionJenkins project is thrivingUsers & devs are voting with their feetMore formal & transparent governanceNew initiativesNew release modelBetter plugin compatibility testingPlugin development for other languages

Q&AUpcoming Meetups 4/13 San Francisco 5/1 Paris 5/20 Tokyo 5/28 HamburgResourceshttp://jenkins-ci.org/ Twitter: @jenkinsci

This document discusses building software as a social challenge that requires sharing tasks, ideas, and code through tools for issue and project tracking, source code management, team collaboration, and continuous integration. It emphasizes that culture and tools are important ingredients for software development and highlights practices like ShipIt Days, Planning Poker, and transparent development processes. Examples of tools and plugins developed by Atlassian employees to improve collaboration are also listed.

Devops and git basicsSourabh Saxena

This document provides an overview of DevOps, Git basics, and their relationship. It discusses how DevOps aims to improve collaboration between development and operations teams through practices like continuous integration, continuous delivery, and infrastructure automation. It also introduces some key DevOps terminology. Additionally, it covers the basics of using Git for version control, including tracking files, staging changes, committing, ignoring files, and pushing/pulling from remote repositories.

London HUG 14/4 - Infratructure mgmtLondon HashiCorp User Group

The document discusses the evolution of infrastructure management from traditional configuration management and snowflake servers to more modern approaches like immutable infrastructure, disposable infrastructure, and immutable infrastructure. It notes the benefits of immutable infrastructure in allowing single line of code changes to be deployed on a reliable and repeatable basis, and also discusses using disposable environments for disaster recovery. The presentation raises questions at the end about these approaches.

Jenkins - From Continuous Integration to Continuous DeliveryVirendra Bhalothia

Continuous Delivery is a process that merges Continuous Integration with automated deployment, test, and release; creating a Continuous Delivery solution. Continuous Delivery doesn't mean every change is deployed to production ASAP. It means every change is proven to be deployable at any time. We would see how we can enable CD with Jenkins. Please check out The Remote Lab's DevOps offerings: www.slideshare.net/bhalothia/the-remote-lab-devops-offerings http://theremotelab.io

Jenkins CIhaochenglee

This document provides an overview and introduction to Jenkins, an open-source automation server for continuous integration. It discusses what continuous integration is, best practices for CI, how Jenkins works and its features. Key points include that Jenkins allows automating the build, test and deployment process, has a large plugin ecosystem, and can be used to build projects in many languages beyond Java. The document also demonstrates how to set up and use basic Jenkins functionality.

Scaling Jenkins Udaypal Aarkoti

The document discusses scaling Jenkins, an open source automation server. It notes that over 83% of users consider Jenkins mission critical. Scaling Jenkins involves increasing the number of slaves, jobs, builds and concurrent HTTP requests. It also involves deciding between a single or multiple masters. The document outlines factors to consider when managing Jenkins at large scale like security, plugins, resource utilization and high availability. It presents a reference architecture with multiple Jenkins masters, load balancers, shared build nodes, and centralized management and access controls.

What is Jenkins | Jenkins Tutorial for Beginners | EdurekaEdureka!

****** DevOps Training : https://www.edureka.co/devops ****** This DevOps Jenkins Tutorial on what is Jenkins ( Jenkins Tutorial Blog Series: https://goo.gl/JebmnW ) will help you understand what is Continuous Integration and why it was introduced. This tutorial also explains how Jenkins achieves Continuous Integration in detail and includes a Hands-On session around Jenkins by the end of which you will learn how to compile a code that is present in GitHub, Review that code and Analyse the test cases present in the GitHub repository. The Hands-On session also explains how to create a build pipeline using Jenkins and how to add Jenkins Slaves. The Hands-On session is performed on an Ubuntu-64bit machine in which Jenkins is installed. To learn how Jenkins can be used to integrate multiple DevOps tools, watch the video titled 'DevOps Tools', by clicking this link: https://goo.gl/up9iwd Check our complete DevOps playlist here: http://goo.gl/O2vo13 Facebook: https://www.facebook.com/edurekaIN/ Twitter: https://twitter.com/edurekain LinkedIn: https://www.linkedin.com/company/edureka

How to improve the quality of your applicationEUR ING Ioannis Kolaxis MSc

This document provides tips for improving software quality by focusing on frequently changing code and organizational structure. It recommends (1) refactoring the most complex and frequently changing files, (2) focusing testing on these files, and (3) paying attention to minor contributors and code ownership to reduce defects. Measuring changes at the file level and organizational metrics like minor contributors and ownership can provide insight into where to focus quality efforts.

Standardizing Jenkins with CloudBees Jenkins TeamDeborah Schalm

Jenkins’ extensibility is one of its greatest strengths, but with it comes with some challenges around inconsistent compatibility, quality, and security in its 1300+ components and integrations. CloudBees Jenkins Team is a curated Jenkins distribution that gives small organizations and teams a more stable and secure Jenkins foundation for their continuous delivery journey. In this webinar, we covered: Standardizing a Jenkins environment with CloudBees Jenkins Team Enabling simple component management using the CloudBees Assurance Program Performing one-click upgrades to maximize instance stability with Beekeeper Upgrade Assistant Resolving compliance issues with Beekeeper Upgrade Assistant

Continuous Integration (CI) - An effective development practiceDao Ngoc Kien

Perforce Innovations Showcase Perforce

Jumping from Continuous Integration to Continuous Delivery with Jenkins Enter...CloudBees

The document discusses jumping from continuous integration (CI) to continuous delivery (CD) with Jenkins Enterprise. It provides an overview of Jenkins and Jenkins Enterprise, best practices for CI and CD, and a demo of using Jenkins and Deployit to implement CD for a chess server application across different environments. The presentation aims to help attendees understand how to get started with CD using Jenkins and Deployit.

Louisville Software Engineering Meet Up: Continuous Integration Using JenkinsJames Strong

Transforming Organizations with CI/CDCprime

When DevOps talks meet DevOps tactics, companies find that Continuous Integration is the make or break point. And implementing CI is one thing, but sustainable CI takes a little bit more consideration. CI is not all about releases, it is also about knowing more about how your software delivery pipeline works, it's weak points, and how you are doing over time. Join CloudBees and cPrime as we discuss best practices for facilitating DevOps pipelines with Jenkins Workflow and reveal how the workflow engine of Jenkins CI and “Agilecentric” Devops practices together, support complex control structures, shortens the development cycle, stabilizes environments and reduces defects.

Continuous Integration, Build Pipelines and Continuous DeploymentChristopher Read

This document discusses core concepts and best practices for continuous integration (CI), build pipelines, and deployment. It recommends having a single source code repository, automating builds and testing, publishing the latest build, committing code frequently, building every commit, testing in production environments, keeping builds fast, ensuring all team members can see build status, automating deployment, and making CI and continuous deployment a collaborative effort between developers and system administrators. The goal is to improve quality, time to market, and confidence through practices that provide fast feedback on code changes.

Enterprise CI as-a-Service using JenkinsCollabNet

The document describes a case study of CollabNet implementing a CI-as-a-Service solution for a large financial services company with over 4000 users across 100 teams developing over 150 applications using multiple technologies. The solution involved provisioning Jenkins servers on demand using Lab Management, integrating tools like TeamForge, Subversion, Nexus and SonarQube on a common platform to provide standardized CI tooling and processes managed by a dedicated build engineer. This helped establish a collaborative development culture, improve productivity and reduce costs.

DevOps and Continuous Delivery Reference Architectures - Volume 2Sonatype

CONTINUOUS DELIVERY REFERENCE ARCHITECTURES Including Sonatype Nexus and other popular DevOps tools Derek E. Weeks (@weekstweets) VP and DevOps Advocate Sonatype. Continuous Delivery and DevOps Reference Architectures include many common tool choices. The most common tool choices we find in these reference architectures are: Eclipse, git, Cloudbees Jenkins / Atlassian Bamboo, Sonatype Nexus, Atlassian JIRA, SonarQube, Puppet, Chef, Rundeck, Maven / Ant / Gradle, Subversion (svn), Junit, LiveRebel, ServiceNow

Git slidesNanyak S

#speakgell - Continuous Integration in iconnect360Derek Chan

Jenkins User Conference 東京 2015Kohsuke Kawaguchi

Workflow, container, and beyondKohsuke Kawaguchi

The document discusses Jenkins 2.0 and outlines goals to position Jenkins as a continuous delivery platform. It proposes three pillars for Jenkins 2.0: updated messaging and website to focus on continuous delivery, an improved out-of-the-box experience centered around workflow and pipeline functionality, and targeted internal changes like library upgrades and deprecated API removal. Potential pitfalls are also identified around scope, disruption, backwards compatibility and massive internal changes.

Jenkins 2.0 (日本語)Kohsuke Kawaguchi

開発者を支える生産性向上チームの取り組み -CI, Browser Test, Tools and Infrastructure-Jumpei Miyata

Effective ES6Teppei Sato

なんたって”DevQA” アジャイル開発とQAの合体が改善を生む - 永田敦氏 #postudyPOStudy

ES6 in PracticeTeppei Sato

サイボウズのフロントエンド開発現在とこれからの挑戦Teppei Sato

This document summarizes a Cybozu Meetup event focused on frontend technologies. It discusses Cybozu's transition from traditional server-rendered web applications to single-page applications built with React. It also covers Cybozu's use of Closure Compiler, TypeScript, JSDoc, and other tools for JavaScript development. Best practices are shared around testing, linting, and integrating third-party code. Accessibility standards and strategies for securely embedding third-party code are also mentioned.

受入試験を自動化したらDevとQAのフィードバックループがまわりはじめた話Jumpei Miyata

Effective Automation 〜変化に強い開発基盤〜Jumpei Miyata

Jenkins user conference 2011Kohsuke Kawaguchi

The document summarizes Jenkins creator Kohsuke Kawaguchi's 2011 State of the Union address about the progress and future of the Jenkins project. Key points include Jenkins transitioning to a legal entity affiliated with SPI for governance, fundraising efforts, infrastructure donations, adoption statistics continuing to show conversion from Hudson to Jenkins, upcoming improvements to the core and plugins, and thanks to sponsors.

More Related Content

What's hot (11)

Standardizing Jenkins with CloudBees Jenkins TeamDeborah Schalm

Continuous Integration (CI) - An effective development practiceDao Ngoc Kien

Perforce Innovations Showcase Perforce

Jumping from Continuous Integration to Continuous Delivery with Jenkins Enter...CloudBees

Louisville Software Engineering Meet Up: Continuous Integration Using JenkinsJames Strong

Transforming Organizations with CI/CDCprime

Continuous Integration, Build Pipelines and Continuous DeploymentChristopher Read

Enterprise CI as-a-Service using JenkinsCollabNet

DevOps and Continuous Delivery Reference Architectures - Volume 2Sonatype

Git slidesNanyak S

#speakgell - Continuous Integration in iconnect360Derek Chan

Standardizing Jenkins with CloudBees Jenkins TeamDeborah Schalm

Continuous Integration (CI) - An effective development practiceDao Ngoc Kien

Perforce Innovations Showcase Perforce

Jumping from Continuous Integration to Continuous Delivery with Jenkins Enter...CloudBees

Louisville Software Engineering Meet Up: Continuous Integration Using JenkinsJames Strong

Transforming Organizations with CI/CDCprime

Continuous Integration, Build Pipelines and Continuous DeploymentChristopher Read

Enterprise CI as-a-Service using JenkinsCollabNet

DevOps and Continuous Delivery Reference Architectures - Volume 2Sonatype

Git slidesNanyak S

#speakgell - Continuous Integration in iconnect360Derek Chan

Viewers also liked (10)

Jenkins User Conference 東京 2015Kohsuke Kawaguchi

Workflow, container, and beyondKohsuke Kawaguchi

Jenkins 2.0 (日本語)Kohsuke Kawaguchi

開発者を支える生産性向上チームの取り組み -CI, Browser Test, Tools and Infrastructure-Jumpei Miyata

Effective ES6Teppei Sato

なんたって”DevQA” アジャイル開発とQAの合体が改善を生む - 永田敦氏 #postudyPOStudy

ES6 in PracticeTeppei Sato

サイボウズのフロントエンド開発現在とこれからの挑戦Teppei Sato

受入試験を自動化したらDevとQAのフィードバックループがまわりはじめた話Jumpei Miyata

Effective Automation 〜変化に強い開発基盤〜Jumpei Miyata

Jenkins User Conference 東京 2015Kohsuke Kawaguchi

Workflow, container, and beyondKohsuke Kawaguchi

Jenkins 2.0 (日本語)Kohsuke Kawaguchi

開発者を支える生産性向上チームの取り組み -CI, Browser Test, Tools and Infrastructure-Jumpei Miyata

Effective ES6Teppei Sato

なんたって”DevQA” アジャイル開発とQAの合体が改善を生む - 永田敦氏 #postudyPOStudy

ES6 in PracticeTeppei Sato

サイボウズのフロントエンド開発現在とこれからの挑戦Teppei Sato

受入試験を自動化したらDevとQAのフィードバックループがまわりはじめた話Jumpei Miyata

Effective Automation 〜変化に強い開発基盤〜Jumpei Miyata

Similar to Current state of Jenkins (20)

Jenkins user conference 2011Kohsuke Kawaguchi

CiMallikarjuna G D

The document discusses continuous integration tools Hudson and Jenkins. Hudson was originally created by Sun Microsystems but later renamed to Jenkins after Oracle acquired Sun. Jenkins is an open source automation server that supports continuous integration practices. It allows developers to integrate code changes frequently and automatically test the code and detect errors. The document compares features of Hudson and Jenkins and explains why Jenkins may be preferable to use.

Jenkins OverviewAhmed M. Gomaa

Jenkins User Conference 2012 San FranciscoKohsuke Kawaguchi

This document summarizes Kohsuke Kawaguchi's presentation at the 2012 Jenkins User Conference. Some key highlights include: a new Jenkins release was downloaded 48,000 times filling 513 DVDs; 3.5 new plugins and 25 new plugin versions were released with 500,000 downloads; 80 tickets were filed and 50 were solved; and 145 commits were made to the Jenkins codebase. Kawaguchi also discussed upcoming improvements to areas like the frontend, backend, plugin development, and more international Jenkins events.

Transformation of the Jenkins User Interface and Where it's Going NextTimJacomb1

In this breakout session, fellow practitioners, Jan Faracik and Tim Jacomb, will take a brief look at the history of the Jenkins user interface, a look at where we are currently, and a look at where we want to take the interface in the future. They will discuss the work the community has done to get Jenkins where it is today and the lessons learned along the way. They will also demonstrate the latest Jenkins user interface and preview concepts of where we're headed. They will show how plugin developers can integrate these changes using the new Jenkins Design Library. And talk about how members can get more involved in the Jenkins community. If you want a sneak preview of some of the work in progress, check out the latest Jenkins weekly release: https://weekly.ci.jenkins.io as well as in the new Jenkins Design Library: https://weekly.ci.jenkins.io/design-library/

Continuous Integration (Jenkins/Hudson)Dennys Hsieh

Jenkins is an open-source tool for continuous integration that allows developers to integrate code changes frequently from a main branch using an automated build process. It detects errors early, measures code quality, and improves delivery speed. Jenkins supports various source control, build tools, and plugins to customize notifications and reporting. Security features allow restricting access and privileges based on user roles and projects.

varun JENKINS.pptxVgPolampalli

This document provides information on Jenkins, including: - Jenkins is an open source automation tool that allows continuous integration and delivery of software projects. It builds, tests, and prepares code changes for release. - Key benefits of Jenkins include speeding up the software development process through automation, integrating with many testing and deployment technologies, and making it easier for developers to integrate changes and users to obtain fresh builds. - Jenkins uses plugins to integrate various DevOps stages like build, test, package, deploy, etc. It supports pipelines to automate development tasks.

Jenkinspenetration Tester

Jenkins is an open-source tool for continuous integration that was originally developed as the Hudson project. It allows developers to commit code frequently to a shared repository, where Jenkins will automatically build and test the code. Jenkins is now the leading replacement for Hudson since Oracle stopped maintaining Hudson. It helps teams catch issues early and deliver software more rapidly through continuous integration and deployment.

Jenkins - Automating Yourself Out Of A Job (One That You Don't Want)lloydbenson

The challenge - testing the oVirt projectEyal Edri

The document summarizes a presentation about using Foreman, Puppet, and oVirt to build an automated testing framework for the Jenkins continuous integration server. The framework provisions virtual and physical machines from a pool managed by Foreman using Puppet configuration profiles. It integrates with Jenkins through a Foreman plugin that allows jobs to request machines with specific profiles. This allows complex virtualization projects to be tested in Jenkins efficiently and reproducibly without needing many physical resources. Screenshots and a demo were provided of the Foreman web interface, command line usage, and oVirt management console.

Jenkins.pdf326KUBAVATHARSHALBHA

This document provides an introduction to Jenkins, including: - Jenkins is an open source automation server that enables developers to reliably build, test, and deploy software. - It helps automate software development processes like building, testing, and deploying to facilitate continuous integration and delivery. - Jenkins supports continuous integration workflows called pipelines that can be modeled as code in Jenkinsfiles and checked into version control.

Best Practices for Mission-Critical Jenkinsmrooney7828

The Key Components of Adopting CI The OpenStack WayiWeb (group INAP)

Ci in jenkins with openSUSEBen Chou

This document provides an overview of continuous integration using Jenkins. It defines continuous integration and outlines its benefits. It then discusses what Jenkins is, how it works, and why it is commonly used for continuous integration. The document demonstrates how to install Jenkins, launch it, and use plugins to enhance its capabilities. It concludes with a summary of how Jenkins helps automate the build, testing and deployment process to improve agile development.

Continuous integration and deployment with jenkinsMd. Shariful Islam ✅

Continuous integrationYoshan madhumal

This document provides an overview of continuous integration and compares two popular tools: Travis CI and Jenkins. Continuous integration involves regularly integrating code changes into a shared repository. Martin Fowler's definition is provided. The challenges of integration are discussed. Key aspects of continuous integration like building, testing, and archiving are outlined. Benefits like early bug detection are noted. Travis CI and Jenkins are introduced as popular CI tools. Travis CI is a hosted service that integrates with GitHub, while Jenkins is an open-source application. Their features, uses cases, and examples of companies using each tool are summarized.

OSDC 2017 - Julien Pivotto - Automating JenkinsNETWAYS

Jenkins is a unique piece of software, lots of people and enterprises use it to deploy and build their software and also their infrastructure. It has tons of plugins, and can do virtually anything. It is important for both devs and ops. This talk will be about how you can automate and test your Jenkins instances. In the past, the tooling around it was not so great, but it has changed. Tools like Jenkins Pipeline and Job DSL plugin has entered the game and are here to stay.

OSDC 2017 | Automating Jenkins by Julien PivottoNETWAYS

35 Jenkins Interview Questions and Answers for 2023.pdfhimanijain83

An Introduction To JenkinsKnoldus Inc.

Jenkins user conference 2011Kohsuke Kawaguchi

CiMallikarjuna G D

Jenkins OverviewAhmed M. Gomaa

Jenkins User Conference 2012 San FranciscoKohsuke Kawaguchi

Transformation of the Jenkins User Interface and Where it's Going NextTimJacomb1

Continuous Integration (Jenkins/Hudson)Dennys Hsieh

varun JENKINS.pptxVgPolampalli

Jenkinspenetration Tester

Jenkins - Automating Yourself Out Of A Job (One That You Don't Want)lloydbenson

The challenge - testing the oVirt projectEyal Edri

Jenkins.pdf326KUBAVATHARSHALBHA

Best Practices for Mission-Critical Jenkinsmrooney7828

The Key Components of Adopting CI The OpenStack WayiWeb (group INAP)

Ci in jenkins with openSUSEBen Chou

Continuous integration and deployment with jenkinsMd. Shariful Islam ✅

Continuous integrationYoshan madhumal

OSDC 2017 - Julien Pivotto - Automating JenkinsNETWAYS

OSDC 2017 | Automating Jenkins by Julien PivottoNETWAYS

35 Jenkins Interview Questions and Answers for 2023.pdfhimanijain83

An Introduction To JenkinsKnoldus Inc.

More from Kohsuke Kawaguchi (20)

JavaOne 2014: Next Step in Automation: Elastic Build EnvironmentKohsuke Kawaguchi

On sharing ideas & sharing codeKohsuke Kawaguchi

The document discusses open commit policies and pull requests for sharing ideas in code. It argues that an open commit policy allowing all contributors direct commit access may no longer be necessary with tools like GitHub, and that pull requests can be just as effective for collaborating on ideas. However, too many restrictions or processes that create friction for contributors sharing ideas through code can negatively impact an engineering organization's ability to innovate and scale. The document advocates letting people innovate freely and fail fast by getting out of their way and allowing them to share ideas directly in code.

コードの互換性と進化の両立Kohsuke Kawaguchi

Jenkins User Conference 2013: Literate, multi-branch, mobile and moreKohsuke Kawaguchi

The document summarizes the Jenkins User Conference that took place on October 23, 2013 in Palo Alto. It discusses Jenkins reaching its 3 year anniversary and new features like multi-branch capabilities, a literate programming API, and improved support for mobile and cloud technologies. It also describes upcoming Jenkins plugins and initiatives like Jenkins Hybrid and Multi-master that aim to help users manage multiple distributed Jenkins installations.

Jenkins User Conference 2013 Palo Alto: KeynoteKohsuke Kawaguchi

Jenkins State of union 2013Kohsuke Kawaguchi

Kohsuke Kawaguchi gave the state of the union address for Jenkins at the 2013 user conference. Some key updates included improvements to performance and scalability, new testing approaches, and plugins for workflow automation, database integration, and recipe sharing. Going forward, priorities include better support for complex workflows, database storage, and recommendations to help users discover needed plugins.

How we made jenkins communityKohsuke Kawaguchi

- Jenkins is an open source automation server with over 53,000 installations and 600+ plugins created by 500 contributors. It uses a modular architecture and extensibility model to enable large-scale distributed development. - Jenkins succeeded by focusing on extensibility through well-defined extension points, treating extensions as first-class citizens, enabling data and code extensibility, and ensuring extensions are themselves extensible. This reduced communication needs and lowered barriers to contribution. - An update center and shared resources like IRC provided a "center of gravity" to connect contributors and ensure the long-term maintenance of plugins. This self-reinforcing community allowed Jenkins to scale development through extensibility.

第六回Jenkins勉強会Kohsuke Kawaguchi

Large scale automation with jenkinsKohsuke Kawaguchi

1. The document discusses various ways to configure complex workflows in Jenkins using plugins like the Parameterized Trigger Plugin, Multi-Configuration Project, Promoted Builds Plugin, and Fingerprint Plugin. 2. Key aspects covered include passing parameters between jobs, running jobs in parallel configurations, promoting builds between stages like testing and production, and tracking artifacts and dependencies between jobs. 3. Advanced workflow capabilities in Jenkins allow automating multi-step build, test, and deployment processes in a flexible and reusable manner.

Jenkins+Gitによる検証済みマージ(30分版)Kohsuke Kawaguchi

ここ最近のJenkins新機能Kohsuke Kawaguchi

Jenkins user conference 東京Kohsuke Kawaguchi

Dev@cloudの実装Kohsuke Kawaguchi

Developer summit continuous deliveryとjenkinsKohsuke Kawaguchi

Creating a Developer CommunityKohsuke Kawaguchi

The document discusses strategies for creating a developer community around an open source project based on lessons learned from Jenkins. It advocates for making the project highly modular and extensible through a plugin architecture to encourage participation. It also stresses the importance of lowering barriers to contribution by making everything from downloading to building to submitting code as easy as possible. Centralizing updates through a shared update mechanism helps provide a center of gravity for the community.

プロジェクト現状報告・Rubyによるjenkinsプラグイン開発Kohsuke Kawaguchi

Jenkins勉強会第二回Kohsuke Kawaguchi

Jenkins と groovyKohsuke Kawaguchi

ホット・トピック・セミナー「Metro」Kohsuke Kawaguchi

Hudson (JJUG CCCにて)Kohsuke Kawaguchi

JavaOne 2014: Next Step in Automation: Elastic Build EnvironmentKohsuke Kawaguchi

On sharing ideas & sharing codeKohsuke Kawaguchi

コードの互換性と進化の両立Kohsuke Kawaguchi

Jenkins User Conference 2013: Literate, multi-branch, mobile and moreKohsuke Kawaguchi

Jenkins User Conference 2013 Palo Alto: KeynoteKohsuke Kawaguchi

Jenkins State of union 2013Kohsuke Kawaguchi

How we made jenkins communityKohsuke Kawaguchi

第六回Jenkins勉強会Kohsuke Kawaguchi

Large scale automation with jenkinsKohsuke Kawaguchi

Jenkins+Gitによる検証済みマージ(30分版)Kohsuke Kawaguchi

ここ最近のJenkins新機能Kohsuke Kawaguchi

Jenkins user conference 東京Kohsuke Kawaguchi

Dev@cloudの実装Kohsuke Kawaguchi

Developer summit continuous deliveryとjenkinsKohsuke Kawaguchi

Creating a Developer CommunityKohsuke Kawaguchi

プロジェクト現状報告・Rubyによるjenkinsプラグイン開発Kohsuke Kawaguchi

Jenkins勉強会第二回Kohsuke Kawaguchi

Jenkins と groovyKohsuke Kawaguchi

ホット・トピック・セミナー「Metro」Kohsuke Kawaguchi

Hudson (JJUG CCCにて)Kohsuke Kawaguchi

Recently uploaded (20)

A simple Introduction to Algorithmic FairnessPaolo Missier

Wondershare Filmora 14.3.2 Crack + License Key Free for Windows PCMudasir

AI and Gender: Decoding the Sociological ImpactSaikatBasu37

Partner Tableau Next Product First Call Deck.pdfssuser3d62c6

This PDF presentation serves as the introductory deck for a partner call focused on the upcoming Tableau product release, titled "Next Product." It is designed to provide partners with a comprehensive overview of the new features, strategic benefits, and market positioning of the Tableau Next product. The deck covers key product capabilities, integration possibilities, use cases, and partner enablement resources to prepare sales and technical teams for effective customer engagement. Ideal for initial partner briefings, the document aims to align stakeholders on value propositions and foster collaboration for successful product adoption.

MCP Dev Summit - Pragmatic Scaling of Enterprise GenAI with MCPSambhav Kothari

Dr Schwarzkopf presentation on STKI Summit ADr. Jimmy Schwarzkopf

Introduction and Background: Study Overview and Methodology: The study analyzes the IT market in Israel, covering over 160 markets and 760 companies/products/services. It includes vendor rankings, IT budgets, and trends from 2025-2029. Vendors participate in detailed briefings and surveys. Vendor Listings: The presentation lists numerous vendors across various pages, detailing their names and services. These vendors are ranked based on their participation and market presence. Market Insights and Trends: Key insights include IT market forecasts, economic factors affecting IT budgets, and the impact of AI on enterprise IT. The study highlights the importance of AI integration and the concept of creative destruction. Agentic AI and Future Predictions: Agentic AI is expected to transform human-agent collaboration, with AI systems understanding context and orchestrating complex processes. Future predictions include AI's role in shopping and enterprise IT.

Reducing Bugs With Static Code Analysis php tek 2025Scott Keck-Warren

Managing Geospatial Open Data Serverlessly [AWS Community Day CH 2025]Chris Bingham

Pushing the Limits: CloudStack at 25K HostsShapeBlue

Boris Stoyanov took a look at a load testing exercise conducted in the lab. Discovered how CloudStack performs with 25,000 hosts as we explore response times, performance challenges, and the code improvements needed to scale effectively -- The CloudStack European User Group 2025 took place on May 8th in Vienna, Austria. The event once again brought together open-source cloud professionals, contributors, developers, and users for a day of deep technical insights, knowledge sharing, and community connection.

Build your own NES Emulator... with KotlinArtur Skowroński

For those who have ever wanted to recreate classic games, this presentation covers my five-year journey to build a NES emulator in Kotlin. Starting from scratch in 2020 (you can probably guess why), I’ll share the challenges posed by the architecture of old hardware, performance optimization (surprise, surprise), and the difficulties of emulating sound. I’ll also highlight which Kotlin features shine (and why concurrency isn’t one of them). This high-level overview will walk through each step of the process—from reading ROM formats to where GPT can help, though it won’t write the code for us just yet. We’ll wrap up by launching Mario on the emulator (hopefully without a call from Nintendo).

How to Integrate FME with Databricks (and Why You’ll Want To)Safe Software

Databricks is a powerful platform for processing and analyzing large volumes of data at scale. But when it comes to connecting systems, transforming messy data, incorporating spatial data, or delivering results across teams – FME can take your Databricks implementation even further. In this webinar, join our special guest speaker Martin Koch from Avineon-Tensing as we explore how FME and Databricks can work together to streamline your end-to-end data journey. In this webinar, you’ll see live demos on how to: -Moving data in and out of Databricks using FME WebApps -Integrating Databricks with ArcGIS for spatial analysis -Creating a data virtualization layer on top of Databricks You’ll also learn how FME enhances interoperability, automates routine tasks, and helps deliver trusted, ready-to-use data into and out of your Databricks environment. If you’re using Databricks, or considering it, this webinar will show you how pairing it with FME can maximize both platforms’ strengths and deliver even more value from your data strategy.

AI Unboxed - How to Approach AI for Maximum ReturnMerelda

Keynote for a client. In this session, Merelda addressed common misconceptions about AI technologies, particularly the confusion between Predictive AI and Generative AI, and provided clarity on when to use each. Predictive AI analyzes historical data to forecast future outcomes, while Generative AI creates new content, from text to images, rapidly. Understanding the differences between these technologies is crucial for making informed, strategic decisions. She introduced the three archetypes of AI adoption: Takers, Shapers, and Makers, inviting the audience to identify which role their organisation plays. Based on these archetypes, she presented industry-specific examples relevant to Schauenburg’s portfolio, showcasing how Predictive AI can drive operational efficiency (e.g., predicting equipment maintenance), while Generative AI enhances customer interactions (e.g., generating technical documents). The session received a 10/10 rating from attendees for its practical insights and immediate applicability.

Multi-Agent AI Systems: Architectures & Communication (MCP and A2A)HusseinMalikMammadli

Breaking it Down: Microservices Architecture for PHP Developerspmeth1

Transitioning from monolithic PHP applications to a microservices architecture can be a game-changer, unlocking greater scalability, flexibility, and resilience. This session will explore not only the technical steps but also the transformative impact on team dynamics. By decentralizing services, teams can work more autonomously, fostering faster development cycles and greater ownership. Drawing on over 20 years of PHP experience, I’ll cover essential elements of microservices—from decomposition and data management to deployment strategies. We’ll examine real-world examples, common pitfalls, and effective solutions to equip PHP developers with the tools and strategies needed to confidently transition to microservices. Key Takeaways: 1. Understanding the core technical and team dynamics benefits of microservices architecture in PHP. 2. Techniques for decomposing a monolithic application into manageable services, leading to more focused team ownership and accountability. 3. Best practices for inter-service communication, data consistency, and monitoring to enable smoother team collaboration. 4. Insights on avoiding common microservices pitfalls, such as over-engineering and excessive interdependencies, to keep teams aligned and efficient.

NVIDIA’s Enterprise AI Factory and Blueprints_ Paving the Way for Smart, Scal...derrickjswork

In a landmark step toward making autonomous AI agents practical and production-ready for enterprises, NVIDIA has launched the Enterprise AI Factory validated design and a set of AI Blueprints. This initiative is a critical leap in transitioning generative AI from experimental projects to business-critical infrastructure. Designed for CIOs, developers, and AI strategists alike, these new offerings provide the architectural backbone and application templates necessary to build AI agents that are scalable, secure, and capable of complex reasoning — all while being deeply integrated with enterprise systems.

Introducing High Availability: Business Continuity for Every NAS UserQNAP Marketing

The fundamental misunderstanding in Team TopologiesPatricia Aas

MuleSoft RTF & Flex Gateway on AKS – Setup, Insights & Real-World TipsPatryk Bandurski

This presentation was delivered during the Warsaw MuleSoft Meetup in April 2025. Paulina Uhman (PwC Polska) shared her hands-on experience running MuleSoft Runtime Fabric (RTF) and Flex Gateway on Azure Kubernetes Service (AKS). The deck covers: What happens after installation (pods, services, and artifacts demystified) Shared responsibility model: MuleSoft vs Kubernetes Real-world tips for configuring connectivity Key Kubernetes commands for troubleshooting Lessons learned from practical use cases 🎙️ Hosted by: Patryk Bandurski, MuleSoft Ambassador & Meetup Leader 💡 Presented by: Paulina Uhman, Integration Specialist @ PwC Polska

PSEP - Salesforce Power of the Platform.pdfssuser3d62c6

This PDF document is a presentation for the Salesforce Partner Success Enablement Program (PSEP), focusing on the "Power of the Platform." It highlights Salesforce’s core platform capabilities, including customization, integration, automation, and scalability. The deck demonstrates how partners can leverage Salesforce’s robust tools and ecosystem to build innovative business solutions, accelerate digital transformation, and drive customer success. It serves as an educational resource to empower partners with knowledge about the platform’s strengths and best practices for solution development and deployment.

Storage Setup for LINSTOR/DRBD/CloudStackShapeBlue

Deciding on a good storage layout is crucial for good performance and reliability on later operations of your LINSTOR/CloudStack installation. This session gave the attendees an overview on different storage setups (LVM-Thin, striping, ZFS) and explaining differences in failure domains and performance implications and how to use them in LINSTOR. -- The CloudStack European User Group 2025 took place on May 8th in Vienna, Austria. The event once again brought together open-source cloud professionals, contributors, developers, and users for a day of deep technical insights, knowledge sharing, and community connection.

A simple Introduction to Algorithmic FairnessPaolo Missier

Wondershare Filmora 14.3.2 Crack + License Key Free for Windows PCMudasir

AI and Gender: Decoding the Sociological ImpactSaikatBasu37

Partner Tableau Next Product First Call Deck.pdfssuser3d62c6

MCP Dev Summit - Pragmatic Scaling of Enterprise GenAI with MCPSambhav Kothari

Dr Schwarzkopf presentation on STKI Summit ADr. Jimmy Schwarzkopf

Reducing Bugs With Static Code Analysis php tek 2025Scott Keck-Warren

Managing Geospatial Open Data Serverlessly [AWS Community Day CH 2025]Chris Bingham

Pushing the Limits: CloudStack at 25K HostsShapeBlue

Build your own NES Emulator... with KotlinArtur Skowroński

How to Integrate FME with Databricks (and Why You’ll Want To)Safe Software

AI Unboxed - How to Approach AI for Maximum ReturnMerelda

Multi-Agent AI Systems: Architectures & Communication (MCP and A2A)HusseinMalikMammadli

Breaking it Down: Microservices Architecture for PHP Developerspmeth1

NVIDIA’s Enterprise AI Factory and Blueprints_ Paving the Way for Smart, Scal...derrickjswork

Introducing High Availability: Business Continuity for Every NAS UserQNAP Marketing

The fundamental misunderstanding in Team TopologiesPatricia Aas

MuleSoft RTF & Flex Gateway on AKS – Setup, Insights & Real-World TipsPatryk Bandurski

PSEP - Salesforce Power of the Platform.pdfssuser3d62c6

Storage Setup for LINSTOR/DRBD/CloudStackShapeBlue

Current state of Jenkins

1. JenkinsProject UpdateKohsuke Kawaguchi

2. DivorceInfra issues in java.net led to the question over the control by Oracle (Nov 2010)Trademark was used as a weaponLed to discussion with Oracle offline to transfer the trademark custody to 3rd party foundationNegotiation failed. Vote proposed to rename Hudson to Jenkins (Jan 2011)Subsequently approved by 214-to-14

3. Jenkins Project Since Thenhttp://jenkins-ci.org/3 people interim governance boardMyselfAndrew Bayer from ClouderaDean Yu from YahooIn process of …Registering trademarkSeeking an umbrella organization for holding assets, CLA, etc.

4. Development in Jenkins ProjectMost Hudson developers moved to Jenkins733 commits since the divorce (vs 172)42% by community (vs 1%)By 48 people (vs 7)More contributions after divorce170 pull requests (vs 20)11.3 change log items per release (vs 6.7 before)94 publicized committers on GitHub (vs 4)496 repositories (vs 1)

5. Development in Jenkins ProjectPlugin development moved to JenkinsShowing # of commits in Hudson pluginsOf 25 top plugins21 moved to Jenkins4 had no commits40 new plugins since the split (vs 1)

6. Delivering what users needIterative, compatible improvements over the codebaseChanges that actually deliver values to usersJust like we’ve been doing all alongBugs/RFEs are getting delivered282 tickets fixed (vs 68)514 tickets created (vs 129)

7. Users are followingPublic Hudson sites moving to JenkinsApache, JRuby, NASA, Nuxeo, Scala, PiWiki, CreativeCommons, OpenIndiana, …Users list traffic1280 e-mails (vs 259)Downloads are healthy8132 war, 2733 deb, 1237 rpm, 1320 zip (per week)OS Distributions are switchingUbuntu, FreeBSD, OpenBSD

8. Users are following

9. New InitiativesBi-weekly governance meetingHeld on IRC, open to everyoneDiscuss project issues and ideasMinutes open to anyone: http://meetings.jenkins-ci.org/Turns out very useful in …Getting fresh people into projectCreating stronger bonds among developers

10. “Stable But Older” Release LineMain release lineThe main release line continues as isEach releases goes through all our automated testsFork a maintenance branch every 3 months from a releaseOnly proven backported fixes from mainlineMonthly releaseHopefully 1.400.1 in May

11. Goal of “Stable But Older” Release LineHelp those who value stability more than new featuresSlower release cycles, more conservative changesProvide focal point for people doing their own QAOften a team in large company does this

12. Plugin compatibility testingFrederic Camblor is driving this effortRerun plugin tests against the latest version of JenkinsShould help us catch regressions earlier

13. Plugins in JRubyCharles Lowell is driving this effortJenkins used more and more in languages like Ruby, PHP, PythonThose users would like to write plugins in their languages, not in JavaHopefully attract new wave of plugin developers

14. My Focus in CoreServe plugin developers technicallyMore extension pointsBetter cross-referencing existing pluginsTechnologies to simplify their codeServe plugin developers sociallyHackathons, documentationRestore infrastructure support

15. My Focus in CoreContinue housekeeping workImproved modularityBug fixes, better error diagnostics, smoothing out rough edgesBetter native packagingPush features along development themesBut do so by writing plugins

16. New Logo Contest: Run-offCloses next Monday

17. ConclusionJenkins project is thrivingUsers & devs are voting with their feetMore formal & transparent governanceNew initiativesNew release modelBetter plugin compatibility testingPlugin development for other languages

18. Q&AUpcoming Meetups 4/13 San Francisco 5/1 Paris 5/20 Tokyo 5/28 HamburgResourceshttp://jenkins-ci.org/ Twitter: @jenkinsci

Current state of Jenkins

Recommended

More Related Content

What's hot (11)

Viewers also liked (10)

Similar to Current state of Jenkins (20)

More from Kohsuke Kawaguchi (20)

Recently uploaded (20)

Current state of Jenkins