This event has ended. View the official site or create your own event → Check it out
This event has ended. Create your own
View analytic
Wednesday, May 14 • 11:00am - 11:40am
Jenkins moving forward

Sign up or log in to save this to your schedule and see who's attending!

We have reached the limit of Jenkins before with the need to continually grow our master Jenkins nodes. With zuul, gearman, nodepool and all the other work that infra has taken on to improve CI is it time to visit replacing Jenkins with an alternative?

I'd like to discuss the critical path towards replacing Jenkins. Specifically what features are required by a potential test runner (such as turbo-hipster) to fulfill infra's needs. For example, should we be looking at providing feature-parity with existing JJB files (ie workers able to interpret job requirements from JJB) or should we take this opportunity to redefine jobs into a subset of Jenkins modules/features?

An implementation strategy should also be thought of. For example, do we have the resources to run every job twice to compare Jenkins' results to another system? If not, how many jobs should we compare (10% etc?). Or maybe we just compare in an experimental pipeline. Regardless I think for a while we will have an overlap where we need to run Jenkins for more complicated to port jobs.

(Session proposed by Joshua Hesketh)

Wednesday May 14, 2014 11:00am - 11:40am

Attendees (49)