[
https://issues.apache.org/jira/browse/GEODE-6340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16765204#comment-16765204
]
ASF subversion and git services commented on GEODE-6340:
--------------------------------------------------------
Commit 0a29ba4762f3a79906534ffd22668405e9aacf0a in geode-benchmarks's branch
refs/heads/develop from Helena Bales
[ https://gitbox.apache.org/repos/asf?p=geode-benchmarks.git;h=0a29ba4 ]
GEODE-6340: add optional metadata to benchmark run (#50)
* GEODE-6340: add optional metadata to benchmark run
* add a metadata.json file to the test results
* get metadata from -Pmetadata in gradle command
* add cli option for metadata in run_test and run_against_benchmark
* change benchmark branch cli option from -m to -e
* update cli help message
* add default metadata values including branch names and versions
* update readme and add closing parens to help
* appease spotless
> Add arbitrary key=value metadata to benchmark runs.
> ---------------------------------------------------
>
> Key: GEODE-6340
> URL: https://issues.apache.org/jira/browse/GEODE-6340
> Project: Geode
> Issue Type: Improvement
> Components: benchmarks
> Reporter: Helena Bales
> Priority: Major
> Labels: pull-request-available
> Time Spent: 40m
> Remaining Estimate: 0h
>
> User should be able to add arbitrary key=value pair metadata to a benchmark
> run. The key=value pairs should be stored in the benchmark output in a known
> location.
> Example (not required implementation):
> ./gradlew benchmark -Phosts=... -PoutputDir=... -Pmetadata=k1=v1,k2=v2
> output/.../metadata.json:
> {
> "k1":"v1",
> "k2":"v2"
> }
> Acceptance:
> Command line option for providing key=value pairs.
> File containing the key=value pairs.
> Arguments can be provide through all helper scripts.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
