Feature request: Have hubble updater run as part of a CI job or Heroku

So far, the hubble updater can either be installed on the GitHub Enterprise machine or run as a cron job from a separate machine. Having it as a service on GitHub Enterprise itself has the drawback, that you need to reinstall it after every upgrade, having it running on a separate machine has the drawback that you have to find, secure and properly maintain this other machine. In both cases, some manual setups steps are required.

I wonder whether it would be possible to use a CI service like Travis or Jenkins or a free Heroku app to run hubble updater once a day. All systems provide a declarative approach to define their build / run steps + encrypted environment variables for the credentials needed to connect to GitHub Enterprise. With Heroku, one could even come up with a [Heroku deploy button](https://devcenter.heroku.com/articles/heroku-button).

Start by reviewing the updater's current installation and cron-job setup, then compare the CI services and Heroku deployment approach named in the issue. Define one supported daily execution path with declarative run steps and encrypted GitHub Enterprise credentials; done means the updater runs without a separately maintained machine or post-upgrade reinstall.

Written by the indexing model from the issue text.