DevOps LifeCycle / Feedback Loop

Feedback everywhere

We want feedback, not only when applications are in production, but everywhere. PullRequest, build, Release, Monitoring, etc…

Following examples show how we are using Tat through our DevOps lifecycle @ OVH.

First of all, TaT was designed to be a hub of all Continuous Delivery and DevOps communcation. By plugin all the software running in Plug all the software running in your DevOps ecosystem to Tat, you’ll be able to follow all the things in TaT and improve as well team and machines collaboration]

Plan :

Code :

Build And Tests :

Release :

Monitor :

Plan

Starting the DevOps lifcycle with an agile view designed to plan your next release/iteration

Code

Follow Pull Request, and share pieces of Code

Build & Test

Follow Continuous Integration, Continuous Delivery Pipelines through a pipeline views. Here shown with CDS (lien vers CDS).

Release

End of your cycle commitment: build automatically your release note from your git repository, JIRA …

Deploy

Monitor

Build your own dashing view, monitor things with a light Terminal UI, showing resources heatmap of planning your interventions..

Feedback