At work, it is pretty common to have a pipeline step that compiles the code & runs the unit tests, otherwise your commit fails.
Is anyone also having a benchmark step, where part of the code is benchmarked, in order to compare the performance in the current commit with that of previous ones ?
Any advice on how to set up one ? CPU intensive flow - I benchamrk it, then I want every commit to see how my current benchmark compares to old ones - any idea on how to achieve this using gitlab ?
How do I store benchmark results between runs of the benchmark pipeline steps ?
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.