We totally want to do this with GitLab CI. Right now you can have GitLab CI measure your code coverage, see <a href="https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab-ci&#x2F;commit&#x2F;96b17c1735b655f33735eb306f3054dfba752cf6&#x2F;builds" rel="nofollow">https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab-ci&#x2F;commit&#x2F;96b17c1735b65...</a> for an example. We can just add a graph and allow people to add more metrics <a href="https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab-ce&#x2F;issues&#x2F;13409" rel="nofollow">https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab-ce&#x2F;issues&#x2F;13409</a><p>Obviously you should ensure that your performance tests are run on the same type of machine every time. But you can do this by labeling runners.