[
https://issues.apache.org/jira/browse/GEODE-6340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16765419#comment-16765419
]
ASF subversion and git services commented on GEODE-6340:
--------------------------------------------------------
Commit 83fc3e2073c78d212de063d38e4532690336f082 in geode's branch
refs/heads/feature/GEODE-6277 from Helena Bales
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=83fc3e2 ]
GEODE-6340: use new cli options for benchmarks (#3148)
* GEODE-6340: use new cli options for benchmarks
* change geode benchmark branch from -m to -e
* use the new -m option to specify metadata for ci runs of benchmarks
> 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: 50m
> 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)
