OK, it turned out most things I needed were provided in the core Jenkins templates. PR is here: https://github.com/jenkinsci/jenkins/pull/960. Is there a contribution guideline<https://github.com/blog/1184-contributing-guidelines>for Jenkins?
On a related note, it would be really nice if there was an endpoint to retrieve environment variables, or some form of configuration, via the REST API, but this is probably venturing into plugin territory and away from theming/skinning. On Sunday, September 29, 2013 6:34:20 AM UTC-7, Dominik Bartholdi wrote: > > No big deal, open PR's for whatever you think is required… > Just be aware that many elements might also be contributed by different > plugins and you might have to open PR's to these too. > /Domi > > On 29.09.2013, at 00:05, Kevin Burke <[email protected] <javascript:>> > wrote: > > Hi, > I made a custom theme for Jenkins entirely in CSS and JS: > https://github.com/kevinburke/doony. It is not cross-browser compatible, > and almost certainly contains bugs, but it works for my use case and I am > pretty happy with it at the moment. > > Implementing accurate CSS selectors and doing DOM traversal in JS was > pretty difficult because many times the Jenkins UI does not contain unique > selectors or classes for elements. > > For example, the "Console Output" is a raw <pre> tag embedded in a > <table>. Styling it requires CSS like so: > > #main-panel > pre { > > Sadly this will apply to any <pre> elements nested directly under the > #main-panel ID; there's no way to get more specific to the console output. > > *I'd like to add ID's and classes to some common HTML elements in Jenkins. > * For example, the Console Output HTML would change from: > > <td id="main-panel" width="80%" height="100%"> > <pre> > Started by user ... > </pre> > </td> > > To: > > <td id="main-panel" width="80%" height="100%"> > <pre id="console-output"> > Started by user ... > </pre> > </td> > > What do you think? If it sounds good I will make the change and submit a > pull request. > > Best, > Kevin > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] <javascript:>. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
