Maybe it's a security issue (for us it doesn't seem to be), but wouldn't it be enough to get rid of the wrapping <pre> element and add HTML escaping?

Yeah, I came here to file this exact CR, found this and voted for it instead.

Outputting HTML tables and such would be huge . . . though I suspect it would require Jenkins support.

If security is the issue (mentioned above), about about at least allow us to create a HTML page "someplace" and provide a link to it. That way you could build the results in HTML and make it easy for the user to browse to it. This does have problems though given multiple users from multiple clients . . . you need someplace to store the HTML and some kind of clean up function for when the user is done with it (or 2 days later) . . .

Frank

I guess for most use cases it would be enough to allow links to jobs and builds. At least for everything I wanted to create links in Groovy scripts for that would do...

Code changed in jenkins
User: imod
Path:
src/main/resources/org/jenkinsci/plugins/scriptler/ScriptlerManagment/runscript.jelly
http://jenkins-ci.org/commit/scriptler-plugin/20636e7b887de37cb00abb3a7cd36f89ae4f5c40
Log:
[FIXED JENKINS-10839] Allow for HTML output in scriptler

Compare: https://github.com/jenkinsci/scriptler-plugin/compare/fe0d444...20636e7

Integrated in plugins_scriptler #44
[FIXED JENKINS-10839] Allow for HTML output in scriptler (Revision 20636e7b887de37cb00abb3a7cd36f89ae4f5c40)

Result = SUCCESS
imod :
Files :

• src/main/resources/org/jenkinsci/plugins/scriptler/ScriptlerManagment/runscript.jelly