rtyler
/
brokenco.de
1
0
Fork 0
Code Pull Requests Releases Activity

Fix references to the now defunct Hudson project. Long live Jenkins!

This commit is contained in:
R. Tyler Croy 2011-09-06 11:31:54 -07:00
parent e08a21e41e
commit 6abf51b06b
1 changed files with 14 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
_posts/2009-06-18-using-glibs-gtester-results-in-hudson.markdown
View File

@ -1,23 +1,31 @@
---
---
layout: post
title: Using Glib's gtester Results in Hudson
tags:
title: Using Glib's gtester Results in Jenkins
tags:
- miscellaneous
- software development
- linux
- hudson
- jenkins
nodeid: 218
created: 1245312122
---
For one of the projects I've been working on lately, I've been making use of [Glib's Testing](http://library.gnome.org/devel/glib/unstable/glib-Testing.html) functionality to write unit tests for a C-based project. I'm a fairly big fan of the [Hudson Continuous Integration Server](http://hudson-ci.org) and I wanted to run tests for my C-based project.
**Update:** (*2011.09.06*) Fixed references to Hudson, which has since been
renamed to [Jenkins](http://www.jenkins-ci.org).
---
For one of the projects I've been working on lately, I've been making use of [Glib's Testing](http://library.gnome.org/devel/glib/unstable/glib-Testing.html) functionality to write unit tests for a C-based project. I'm a fairly big fan of the [Jenkins Continuous Integration Server](http://jenkins-ci.org) and I wanted to run tests for my C-based project.
Unfortunately, the `gtester` application generates XML in a custom format that Hudson cannot understand (i.e. JUnit formatted XML). In order to come up with some JUnit XML, I spent about an hour and a half toying with XSLT for transforming the XML `gtester` generates (see the snippet below).
Unfortunately, the `gtester` application generates XML in a custom format that Jenkins cannot understand (i.e. JUnit formatted XML). In order to come up with some JUnit XML, I spent about an hour and a half toying with XSLT for transforming the XML `gtester` generates (see the snippet below).
I added a shell script build step to the end of the build process that runs:
gtester test_app --keep-going -o=Tests.xml
xsltproc -o tests.junit.xml gtester.xsl Tests.xml
Then I just specified "tests.junit.xml" in the **Publish JUnit test result report** section of the **Post-build Actions** and then Hudson would properly process and post the test results when the job was finished.
Then I just specified "tests.junit.xml" in the **Publish JUnit test result report** section of the **Post-build Actions** and then Jenkins would properly process and post the test results when the job was finished.
<script src="http://gist.github.com/131727.js"></script>