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

[jonico]

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.

[IngoS11]

Only somewhat related, but going into a similar direction and I wanted to hear your thoughts. We have Hubble on a separate machine and we have some other non-Hubble jobs for GitHub running on that same machine. I am toying with the idea to use something like Luigi or Airflow but believe I would need to break up the backed part of Hubble into more modules. Have you guys every thought about something like that?