Jenkins Plug-in that can embed and display an html page
13,091 views
Skip to first unread message
Ken
Jan 16, 2013, 11:50:21 AM1/16/13
to jenkin...@googlegroups.com
Hi everyone. I'm just beginning my adventure into Jenkin's land... One of the requirements I'm looking to solve is with embedding or somehow linking an html page that contains build results (created by a Gallio execution).. For anyone that's used Gallio as a UT framework, it can create a nicely formatted HTML page with all the build output and so on... I'd like to take this output and attach or embed it into the Jenkins reporting after a job has run... Can anyone point me in the direction for making this happen? I'm looking through different plug-ins now to see if any support this type of functionality. Thanks for the help!
Ken
Ken
Mark Waite
Jan 16, 2013, 12:10:55 PM1/16/13
to jenkin...@googlegroups.com
There is an HTML publisher plugin that I've used to display the HTML formatted output from the gcc coverage reporting tool "lcov". It is simple to use the publisher plugin and easy to configure into the job.
The "down side" of using any externally generated HTML is that it does not integrate into Jenkins as elegantly as JUnit test results or NUnit test results, or the other more tool specific plugins.
Mark Waite
From: Ken <hero...@gmail.com>
To: jenkin...@googlegroups.com
Sent: Wednesday, January 16, 2013 9:50 AM
Subject: Jenkins Plug-in that can embed and display an html page
Ken Knudsen
Jan 16, 2013, 12:18:29 PM1/16/13
to jenkin...@googlegroups.com
Thanks, I'll look into that... There's also this plug-in I found...
https://wiki.jenkins-ci.org/display/JENKINS/Summary+Display+Plugin
If it becomes to much of a problem to embed it somehow into the
Jenkins report I could take one path that is easy enough: saving the
outputted UT results (in the nicely formatted way that Gallio
generates it) and then serving up the HTML from an HTTP link... I can
then just link as an HREF to it...
https://wiki.jenkins-ci.org/display/JENKINS/Summary+Display+Plugin
If it becomes to much of a problem to embed it somehow into the
Jenkins report I could take one path that is easy enough: saving the
outputted UT results (in the nicely formatted way that Gallio
generates it) and then serving up the HTML from an HTTP link... I can
then just link as an HREF to it...
Ken Knudsen
Jan 16, 2013, 1:43:44 PM1/16/13
to jenkin...@googlegroups.com
So this plugin is getting me a little close to what I'm looking for...
https://wiki.jenkins-ci.org/display/JENKINS/DocLinks+Plugin
It'll take the files and all recursive directories I specify in a
directory and bundle it up into the job report..problem is that it's
attached to the Document Links of the whole Report, not the individual
build run itself... but this is showing that the functionality I'm
looking for is completely possible, very excite!
https://wiki.jenkins-ci.org/display/JENKINS/DocLinks+Plugin
It'll take the files and all recursive directories I specify in a
directory and bundle it up into the job report..problem is that it's
attached to the Document Links of the whole Report, not the individual
build run itself... but this is showing that the functionality I'm
looking for is completely possible, very excite!
Ken Knudsen
Jan 16, 2013, 4:37:48 PM1/16/13
to VanHaren, Jeremy, jenkin...@googlegroups.com
Hi Jeremy,
Not that I can help much but here’s some of my findings today…
I’ve been using the HTML Publisher with success. Once I figured out
how Jenkins is displaying stuff per build run, what I was expecting to
get published per build run, did… Noting your particular problem, I
created a build run such that a build step would fail before and after
my HTML publish (and one that would fail afterwards) build step… each
time I still received the files I attached through HTML Publish… I’m
guessing the way I’m running thing’s is probably different then your
setup… But here’s a quick outline of my work flow..
Build Steps
1) Build kicks off, build-step to sync projects and build
2) Build is complete, install packages created
Post-Build Actions
1) Take install package, farm off to some testing machine
2) Install package and run Gallio unit tests (I have a custom Gallio
runner that will generate reports to an HTML file or save them to
zips).. so I’m not using the Jenkins Gallio plugin
3) Publish my Gallio HTML report with the ‘Publish HTML reports’ plugin
The result is that each build successfully has its unit test run
report attached to the output which I can view from within Jenkins.
Keep in mind I’m not doing the Master-Slave work flow, that’s next…
But the HTML Reports plug-in is working with my given scenario. Not
sure if any of that will help you at all, but I thought I’d just share
it in case.
On Wed, Jan 16, 2013 at 12:16 PM, VanHaren, Jeremy
<Jeremy....@csgi.com> wrote:
> I have a similar issue, the problem we found with the HTML publisher is that
> it doesn’t publish when the build fails. Given that you probably want to
> look at the report when there is a failed unit test, we found it couldn’t be
> used. It would be nice if there was an option to publish even on a failed
> build. Ideally, we would be able to produce the html and the xml outputs,
> feed the xml into the Jenkins xUnit test results so that we have some of the
> nice tracking, but also publish the html report (even on failure)
>
>
>
> Anybody have any ideas?
>
>
>
> -Jeremy
>
>
Not that I can help much but here’s some of my findings today…
I’ve been using the HTML Publisher with success. Once I figured out
how Jenkins is displaying stuff per build run, what I was expecting to
get published per build run, did… Noting your particular problem, I
created a build run such that a build step would fail before and after
my HTML publish (and one that would fail afterwards) build step… each
time I still received the files I attached through HTML Publish… I’m
guessing the way I’m running thing’s is probably different then your
setup… But here’s a quick outline of my work flow..
Build Steps
1) Build kicks off, build-step to sync projects and build
2) Build is complete, install packages created
Post-Build Actions
1) Take install package, farm off to some testing machine
2) Install package and run Gallio unit tests (I have a custom Gallio
runner that will generate reports to an HTML file or save them to
zips).. so I’m not using the Jenkins Gallio plugin
3) Publish my Gallio HTML report with the ‘Publish HTML reports’ plugin
The result is that each build successfully has its unit test run
report attached to the output which I can view from within Jenkins.
Keep in mind I’m not doing the Master-Slave work flow, that’s next…
But the HTML Reports plug-in is working with my given scenario. Not
sure if any of that will help you at all, but I thought I’d just share
it in case.
On Wed, Jan 16, 2013 at 12:16 PM, VanHaren, Jeremy
<Jeremy....@csgi.com> wrote:
> I have a similar issue, the problem we found with the HTML publisher is that
> it doesn’t publish when the build fails. Given that you probably want to
> look at the report when there is a failed unit test, we found it couldn’t be
> used. It would be nice if there was an option to publish even on a failed
> build. Ideally, we would be able to produce the html and the xml outputs,
> feed the xml into the Jenkins xUnit test results so that we have some of the
> nice tracking, but also publish the html report (even on failure)
>
>
>
> Anybody have any ideas?
>
>
>
> -Jeremy
>
>
Reply all
Reply to author
Forward
0 new messages