Re:Choose GitLab for your next open source project
by sytse on Friday February 12, 2016 @09:15PM
(#11092102)
We totally want to do this with GitLab CI. Right now you can have GitLab CI measure your code coverage, see https://gitlab.com/gitlab-org/gitlab-ci/commit/96b17c1735b65... for an example. We can just add a graph and allow people to add more metrics https://gitlab.com/gitlab-org/gitlab-ce/issues/13409
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.
Re:Choose GitLab for your next open source project
by dman on Monday February 15, 2016 @07:56PM
(#11107229)
Thanks for opening the ticket, I have added some comments that capture my use cases to the ticket.
Re:Choose GitLab for your next open source project
by sytse on Monday February 15, 2016 @10:44PM
(#11107762)
Thanks for https://gitlab.com/gitlab-org/gitlab-ce/issues/13409#note_37... I've asked some people to have a look at it in the issue.
One possible workflow -
1. User defines perf metrics in some metadata file in repo.
2. User checks in data for metrics with every commit.
3. Gitlab shows a view of the metrics changing over time.