[CDash] [EXTERNAL] Re: uploading commit info to cdash dashboard

David Cole DLRdave at aol.com
Wed Sep 28 00:22:00 UTC 2016

Yes it would. Sorry, didn't think about that part. I use this technique with primarily individual Experimental builds...


> On Sep 27, 2016, at 8:01 PM, Foucar, James G <jgfouca at sandia.gov> wrote:
> Would that make each build different in the eyes of CMake? Wouldn't that break the +/- feature for new fails and passes?
> From: David Cole <DLRdave at aol.com>
> Date: Tuesday, September 27, 2016 at 5:27 PM
> To: "Foucar, James G" <jgfouca at sandia.gov>
> Cc: "cdash at public.kitware.com" <cdash at public.kitware.com>
> Subject: [EXTERNAL] Re: [CDash] uploading commit info to cdash dashboard
> It wouldn't be easy to hijack one of the fields you mentioned, but it would be fairly easy to encode the first 7 or 8 chars of the commit id into the build name.
> HTH,
> David C.
> On Sep 27, 2016, at 6:12 PM, Foucar, James G <jgfouca at sandia.gov> wrote:
> Hello,
> I'd really like to post the sha1 of the commit that was tested for an individual cdash build. I'd like to display it prominently once the build is clicked. For example, if you look here
> http://my.cdash.org/buildSummary.php?buildid=1056548
> You'll see a number of fields that are not particularly useful to us like OS Name and OS Version. I'd like to replace or hijack one of those fields to instead display the commit id that was tested. How might I go about doing this?
> Thanks,
> -Jim
> _______________________________________________
> CDash mailing list
> CDash at public.kitware.com
> http://public.kitware.com/mailman/listinfo/cdash
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/cdash/attachments/20160927/a05d04fb/attachment-0001.htm>

More information about the CDash mailing list