Jenkins developers will soon notice that jelly files are made up of many diverse jelly tags, and that jelly files live in many places in the Jenkins source tree. The mapping from jelly tag to jelly file or other implementation is tricky to figure out; this page attempts to explain it.
A Jenkins page usually starts with a jelly page named index.jelly. Let's consider src/main/resources/hudson/model/Job/index.jelly. Here's the first line of jelly:
That tag tells us where to find the jelly files or other implementation of tags in the specified namespace:
xmlns:namespace_name="where to find resources in that namespace"
/lib/foo refers to
Let's look at the rest of index.jelly; I've pulled out a few of the interesting pieces:
The first tag we encounter is <l:layout>. The "l" tells us to look in "/lib/layout", because that's what was declared in the j:jelly tag:
I happen to know that
core/src/main/resources/lib/layout/ so to find the source for the l:layout tag, I simply look at
The next tag we encounter is
st:include which declares the
st namespace as somehow related to "jelly:stapler". I suspect this is a jelly feature that I don't know about yet; probably it sends us to a stapler jar for the implementation of the
Let's skip over
l:main-panel, which should be clear already, and jump to
t:editableDescription. The namespace declaration
xmlns:t="/lib/hudson" points us to
Using these simple rules, you can now find the source for jelly tags implemented by Jenkins.