Jenkins : 2.0 JavaScript Modularization

This is a draft document for Jenkins 2.0. None of this is real (yet).


Traditionally, the Jenkins GUI is constructed on the server side from Jelly files (Stapler etc). Client-side JavaScript has not played a big part in the Jenkins GUI.

If the Jenkins GUI is to be modernized and improved (from a user experience perspective), client-side JavaScript needs to be able to play a bigger part. If that's so, we need to modernize/improve the development patterns around how JavaScript is currently used in Jenkins. See here for more discussion on the problem.

Ongoing Efforts

The following are links to some ongoing efforts in the space of JavaScript Modularization:


  • Tom Fennelly, Gus Reiber, Keith Zantow

Related Tickets