Code metrics history

Stefan Nagel_2ly04p

With bibucket pipelines we generate several code metrics like: RAM usage, ROM usage, Unit Test Coverage ... etc.

I would like to have an overview of these metrics over my branch commits. This way I could see e.g. the RAM uasge of my development branch.

Is there any way to do that? Any example or best practise?

I also took a look at Fisheye. Is that coming out of the box with Fisheye? or is it just a small subset on the Fisheye feature and easier to implement by ourselvers.

Any advice would be appreciated.

Kind regards

Stefan

Aron Gombas _Midori_

Fisheye is not available for the Cloud, so if you are using Bitbucket Cloud it wouldn't be a good match.

If I were you, I'd do this:

1. you generate the metric (you're already doing this)
2. from the Pipeline, you can pass metric data to the Segment service (it is a generalized gateway to other analytic services and it has a generous free tier)
3. from Segment you forward the data to an analytic service, we are using Amplitude with great success (but you can choose many other options)
4. in Amplitude, you can easily build charts and reports, then compose dashboards from those which will be auto-updated as your Pipeline is passing more and more analytic data

Notes:

• In step 2, "passing" means a REST API call which you should be able to do easily from the Pipeline.
• You can skip step 2, and pass the data directly to Amplitude. It eliminates one step, but if you want to forward the data to multiple "sinks" or you want to keep the option to choose another sink, then introducing Segment is a good idea!