Benchmark scripts used by an active Jenkins job are archived
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 202
- Forks
- 183
- Avg merge
- 2m
- Merged PRs (30d)
- 1
Description
The benchmark job https://ci.nodejs.org/view/Node.js%20benchmark/job/benchmark-node-micro-benchmarks/ is using the script https://github.com/nodejs/benchmarking/blob/master/experimental/benchmarks/community-benchmark/run.sh to run the benchmarks.
The script is cloning the repo with the HTTP protocol http://github.com/nodejs/node.git (it's been redirected to use HTTPS protocol automatically). Probably worth updating the script to use HTTPS instead.
However, the repository https://github.com/nodejs/benchmarking has been archived and can not be updated. Should we move the benchmarking scripts to a dedicated repo since the benchmarking working group has been de-chartered?
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 experimental/benchmarks/community-benchmark/run.sh in the archived benchmarking repository and the linked Node.js benchmark Jenkins job. Confirm how the script clones node.git and map which benchmarking scripts the job depends on. Done requires a decided repository location for maintainable scripts and an operational benchmark job using the maintained location.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, node.js, shell
- Domain
- ci-cd, devops
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100