# How to run benchmark CI on every commit?

**URL:** <https://discourse.julialang.org/t/how-to-run-benchmark-ci-on-every-commit/27034>\
**Category:** General Usage\
**Tags:** benchmark, ci\
**Created:** [July 31, 2019, 1:40pm UTC](https://discourse.julialang.org/t/how-to-run-benchmark-ci-on-every-commit/27034 "2019-07-31T13:40:28Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![tkf](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tkf/32/17635_2.png) [@tkf](https://discourse.julialang.org/u/tkf)\
**Post date:** [August 1, 2019, 5:52am UTC](https://discourse.julialang.org/t/how-to-run-benchmark-ci-on-every-commit/27034/3 "2019-08-01T05:52:17Z")

</div>

> [@cserteGT3](#):
>
> I can’t use GitHub’s and GitLab’s CI

It’s actually straightforward to setup GitLab CI _runner_ (not entire GitLab service) on machines you control [GitLab Runner | GitLab](https://docs.gitlab.com/runner/). It’s easy if you can use docker [Run GitLab Runner in a container | GitLab](https://docs.gitlab.com/runner/install/docker.html). Once you setup and register the GitLab runner service, you can initiate the job by pushing to [gitlab.com](http://gitlab.com). But this requires the runner service to keep running in the background. So I’m not sure if it fits with your need.

FYI, I setup benchmarks on Travis CI and run a couple of benchmarks: [Home · TransducersBenchmarksReports.jl](https://tkf.github.io/TransducersBenchmarksReports.jl/stable/). I was worried that it may fluctuate a lot. But it turned out Travis is consistent enough for my need. This is because I only care about the performance relative to the baseline implementation I write.

---

_[View the full topic](https://discourse.julialang.org/t/how-to-run-benchmark-ci-on-every-commit/27034)._