Ability to run a benchmark between 2 branches
Open
Nobody has claimed this yet.
ci-job-request
stale
- Dominant language
- Jinja
- Stars
- 541
- Forks
- 185
- Avg merge
- 22h 15m
- Merged PRs (30d)
- 4
Description
Currently, benchmark ci run only compares a branch with a pull request id, but issues like regressions between releases require to benchmark a branch (v18.x) with another branch (v16.x). It would be nice to have a different ci job to compare branches.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the existing benchmark CI job and how it accepts a pull request identifier. Trace where branch references are selected, then define completion as a CI job that can compare two named branches, such as v18.x and v16.x, for regression benchmarking.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs
- Domain
- ci-cd, infrastructure, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100