Jenkins 2. How to make a major OSS project release and not break the community? | CEE-SECR 2016 Jenkins 2. How to make a major OSS project release and not break the community? – CEE-SECR 2016
2019 | 2018 | 2017 | 2016 | 2015 | 2014 | 2013 | 2012 | 2011 | 2010 | 2009 | 2008 | 2007 | 2006 | 2005

Presentations

Jenkins 2. How to make a major OSS project release and not break the community?

Jenkins is a one of the most popular automation servers in the world, which is being widely used in Continuous Integration, Continuous Delivery and DevOps areas. Even after ten years, the project actively evolves. I’m going to talk about the key focuses in the project and its community after the Jenkins 2 release on April 2016. Which lessons did we learn? What changes should be expected? How does it impact Jenkins admins and common users?

Oleg Nenashev

Oleg Nenashev

Jenkins Developer, CloudBees

Jenkins Core Team member, engineer at CloudBees. Oleg has about 8 years of experience in large-scale automation systems for hardware and software projects. In the Jenkins project he works on the core, maintains plugins and also focuses on the community topics. Oleg organizes Jenkins meetups, administers Google Summer of Code in Jenkins and periodically shares his experience at meetups and conferences.

Comment

Your email address will not be published. Required fields are marked *

*

Gold

Deutsche Bank Technology CentreJetBrainsSAPFirst Line Software

Silver

Dell Technologies

Embedded

Auriga

Sponsors

T-SystemsKaspersky Lab

Main partners

RUSSOFTAP KITSECON

In cooperation

Association for Computing MachineryACM Special Interest Group on Software Engineering

Technical partners

Hosting-CenterVirtuozzoSoftInvent7pap StudioPrint SalonGroup MPrezent.ru

With support of

RAEC

Organizers

Software Russiai-Help

The conference is over
See you at CEE-SECR 2017!

Special prices for the hotels and visa support are offered to the conference guests.