( I already had some thoughts on that topic ).


  • Get a better overview of future/pending/past work and keep it.
  • “If you want a developer to do something, e.g. establish a high test coverage, make it easy with sane reasons”


  • Pre-Deployment
    • Feature Branches, consisting of
      • PRs
      • Build
        • (Test) Reports
        • Static Code Analysis (Report?)
        • Build Status green/yellow/red
      • Human Code Analysis (Code Reviews)
  • Post-Deployment
    • Monitoring
      • Active (Alerts)
      • Passive
    • Configuration
      • Feature Flags?


https://prometheus.io https://www.elastic.co/elk-stack https://github.com/cristijora/vue-paper-dashboard


[caption id=“attachment_media-18” align=“aligncenter” width=“2312”]Screen Shot 2018-03-05 at 10.38.27.png a build dashboard at goodle[/caption]

Designing a dashboard for concourse https://medium.com/concourse-ci/designing-a-dashboard-for-concourse-fe2e03248751

[caption id=“attachment_1457” align=“alignnone” width=“2576”]Screen Shot 2018-03-05 at 14.56.33.png foot.it via[/caption]