One more issue in making the Hudson to Jenkins switch...
The Hudson/Jenkins continuous integration server relies on using Jelly scripts, which is considered some type of executable XML format. The format resembles sort of like Django/Jinja2 templates with very little documentation to accompany how it all works. Hudson/Jenkins documents have very few references, so you're left to guess what the statements such as the index.jelly in the Violations plug-in actually do.
One issue encountered was using the Violations plug-in, which allows users to see exactly which lines of code triggered Pylint, PEP8, JSLint-releated errors. The Violations plug-in parses the error codes from these files and supposedly renders the summary similar to how its shown below (taken from https://wiki.jenkins-ci.org/download/attachments/2916418/violations-file-1.png?version=1&modificationDate=1187153094000):

<l:main-panel> <j:set var="model" value="${it.fileModel}"/> <j:set var="image" value="${rootURL}/plugin/violations/images/48x48/dialog-warning.png"/> <j:set var="iconDir" value="${rootURL}/plugin/violations/images/16x16"/> <j:set var="href" value="${it.showLines}"/> <h3><img src="${image}"/> ${model.displayName}</h3> <j:forEach var="t" items="${model.typeMap.entrySet()}"> <table class="pane"> <tbody> <tr><td class="pane-header" colspan="5">${it.typeLine(t.key)}</td></tr> <j:forEach var="v" items="${t.value}"> <tr> <td class="pane"> <j:if test="${href}"> ${v.line} </j:if> <j:if test="${!href}"> ${v.line} </j:if> </td> <!--<td class="pane">${v.source}</td> --> <td class="pane">${it.severityColumn(v)}</td> <td class="pane" width="99%">${v.message}</td> </tr> </j:forEach> </tbody> </table> <p></p> </j:forEach>
/** * Get the display name of this file. * @return the name to use whrn displaying the file violations. */ @Override public String getDisplayName() { return super.getDisplayName(); } /** * Get the map of types to violations. * @return the type to violation map. */ @Override public TreeMap> getTypeMap() { return super.getTypeMap(); }
blog comments powered by Disqus