Hacker News new | past | comments | ask | show | jobs | submit login

The most interesting part of this is the very last paragraph.

There really isn't a good self-hosted solution for build metadata/metrics, unless you write something yourself. It would be interesting to see a GUI dashboard for Drone/whatever builds and pipelines.




I never understood the purpose of dashboards. In the context of CI, I see three use cases and there is always a better solution than a dashboard.

1. Detect broken builds. It is better to actively notify somebody by mail, chat, whatever.

2. Prevent broken master. It is better to reject the pull request/patch before it becomes a problem.

3. Analyse the system. It is better to download the data and enable the use of whatever analysis tools are suitable.


Direct emails can't replace the collaborative "hey why are these still red" moments without spamming the whole team.

They can show non-event information such as build time trends at a glance.


There was an interesting community-driven project to create a dashboard for Drone, see https://github.com/drone/drone-wall. I would love to see more like it.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: