[
https://issues.apache.org/jira/browse/FLINK-28407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-28407:
-----------------------------------
Labels: pull-request-available stale-assigned (was: pull-request-available)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issue is assigned but has not
received an update in 30 days, so it has been labeled "stale-assigned".
If you are still working on the issue, please remove the label and add a
comment updating the community on your progress. If this issue is waiting on
feedback, please consider this a reminder to the committer/reviewer. Flink is a
very active project, and so we appreciate your patience.
If you are no longer working on the issue, please unassign yourself so someone
else may work on it.
> Make Jenkins benchmark script more autonomous
> ---------------------------------------------
>
> Key: FLINK-28407
> URL: https://issues.apache.org/jira/browse/FLINK-28407
> Project: Flink
> Issue Type: Improvement
> Components: Benchmarks
> Reporter: Anton Kalashnikov
> Assignee: Anton Kalashnikov
> Priority: Major
> Labels: pull-request-available, stale-assigned
>
> 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
