Due to some maintenance issues, this service has been switched in read-only mode, you can find more information about the why

and how to migrate your plugin documentation in this blogpost

Skip to end of metadata
Go to start of metadata

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

Problem

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:

Participants

  • Tom Fennelly, Gus Reiber, Keith Zantow

Related Tickets

  • No labels