[FLINK-28407] Make Jenkins benchmark script more autonomous

• Type: Improvement
• Status: In Progress
• Priority: Major
• Resolution: Unresolved
• Component/s: Benchmarks
• Labels: pull-request-available stale-assigned
• Assignee: Anton Kalashnikov
• Reporter: Anton Kalashnikov
• Created: 05/Jul/22 13:19
• Updated: 22/May/23 16:25

Description

Right now, we have Jenkins scripts in the benchmarks repository which contains all logic for launching benchmarks and sending data to Codespeed. But unfortunately, it is not clear to external observers how to use that in case of current Jenkins will be lost.
The suggestion is:

• add information to Readme file about Jenkins and Codespeed.
• add default values to the script rather than keeping them in only Jenkins.

After this task, anybody should be able easily to configure these benchmarks on their own Jenkins + Codespeed.

Issue Links

• links to: GitHub Pull Request #57