GNOME Bugzilla – Bug 631980
Handle an optional <revision> node in the report's XML
Last modified: 2010-12-28 17:07:59 UTC
Just like gtester-reports handles the package name and version it should also handle a particular revision; this is useful for comparing reports coming from different revisions, both in the manual and the automated cases.
Created attachment 172192 [details] [review] gtester-report: Add an optional 'revision' node In order to distinguish reports generated from a specific revision of a projects it would be good if gtester-report handled a <revision> node in the XML. The payload is free-form, just like for the other nodes under <info>.
Created attachment 172193 [details] [review] test: Add a <revision> node to the report XML Use `git describe` to fill out the <revision> node, if we're using a git checkout; otherwise, for tests ran from a released tarball, use the version.
Review of attachment 172192 [details] [review]: Looks fine to me.
Review of attachment 172193 [details] [review]: Looks fine to me.
Attachment 172192 [details] pushed as 52c8310 - gtester-report: Add an optional 'revision' node Attachment 172193 [details] pushed as 500061f - test: Add a <revision> node to the report XML