# 2019.08.06 Hangout

**URL:** <https://discourse.slicer.org/t/2019-08-06-hangout/7893>\
**Category:** Weekly meetings\
**Created:** [August 6, 2019, 12:10pm UTC](https://discourse.slicer.org/t/2019-08-06-hangout/7893 "2019-08-06T12:10:58Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![jcfr](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jcfr/32/17825_2.png) [@jcfr](https://discourse.slicer.org/u/jcfr)\
**Post date:** [August 6, 2019, 6:48pm UTC](https://discourse.slicer.org/t/2019-08-06-hangout/7893/5 "2019-08-06T18:48:53Z")

</div>

> displays something similar to the table in the notebook, auto-generated each day after the builds are (hopefully) finished  
> I will probably do something quick/lazy with github pages to get it up and running.

Makes sense.

Some history: When we used to automatically update the wiki after the build are completed, we were running [this script](https://github.com/Slicer/slicer-wiki-scripts#slicer_wiki_extension_module_listingpy) on each factory, and then we were consolidating all gathered information later that day. This was not very robust.

A simple approach could be to setup a recurrent travis cronjob, that would generate the tables for the current day and previous day every hours. I can point you to an example of such job that is already publishing github pages (this is what we do for the apidocs)

> re: CDash API

Here is some other relevant discussion: [How can I subscribe to monitor individual extensions on Slicer dashboard? - #5 by fedorov](https://discourse.slicer.org/t/how-can-i-subscribe-to-monitor-individual-extensions-on-slicer-dashboard/2261/5)

---

_[View the full topic](https://discourse.slicer.org/t/2019-08-06-hangout/7893)._