Benchmark CI for branches

Hi everyone! Not sure whether this is the right place, but happy to re-open elsewhere if that makes sense:

I’m really digging the benchmark CI functionality that we now have – great work!

Usually, I like to check the benchmarks on something before opening a PR – if the outcome is problematic, I can adjust or rework the changes as needed before it makes sense for the actual review process to start.

For the regular CI or CITGM, that’s pretty easy because we can set the github repository + the git ref name for node-test-commit freely, and it would be awesome if the benchmark CI supported a similar functionality.

I realize that we should run benchmarks locally anyway; but the benchmark CI has the advantage of being fast compared to many developer’s machines, and a dedicated resource (and not battery-draining, for laptop-using devs).

If I can help I’m happy to, but I imagine this is mostly a Jenkins script thing?

Start by locating the benchmark CI and Jenkins configuration, then compare how regular CI or CITGM passes a GitHub repository and git ref to node-test-commit. Done means benchmark CI can run against a selected repository and ref before a pull request exists.