3 ms·
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/96b17
by sytse 11y ago
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/96b17c1735b655f33735eb306f3054dfba752cf6/builds 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 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.
- dman 11y agoThanks for opening the ticket, I have added some comments that capture my use cases to the ticket.
- sytse 11y agoThanks for https://gitlab.com/gitlab-org/gitlab-ce/issues/13409#note_3753579 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.