[
https://issues.apache.org/jira/browse/GEODE-8230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17130854#comment-17130854
]
ASF subversion and git services commented on GEODE-8230:
--------------------------------------------------------
Commit f65ea452443bcd2d0dac6ef1d2d958b0cb02936f in geode's branch
refs/heads/feature/GEODE-8067 from Owen Nichols
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=f65ea45 ]
GEODE-8230: run benchmarks in parallel with other CI jobs (#5217)
* run benchmarks in parallel with other CI jobs
* eliminate JDK11 flavors for deterministic already-required-in-PR-pipeline
jobs UnitTest and ApiChecker
* add Benchmarks tab
> run benchmarks in parallel with other CI
> ----------------------------------------
>
> Key: GEODE-8230
> URL: https://issues.apache.org/jira/browse/GEODE-8230
> Project: Geode
> Issue Type: Improvement
> Components: ci
> Reporter: Owen Nichols
> Assignee: Owen Nichols
> Priority: Major
> Fix For: 1.12.1, 1.13.0, 1.14.0
>
>
> currently, we run Build, then all <x>Test jobs in parallel (which takes ~5
> hours), then all Benchmark<x> jobs (which takes ~5 hours).
> Presumably the benchmarks were run after all tests, on the premise that
> benchmarks are meaningless if the code is not correct. However, required PR
> checks now prevent incorrect code from getting into develop in the first
> place, and the remaining occasional failures are flaky, so it's rather
> arbitrary to gate benchmarks on a lottery.
> However, faster feedback has clear benefits, and cutting our CI pipeline from
> 10 hours to 5 hours seems like low-hanging fruit.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
