-
Task
-
Resolution: Unresolved
-
L3 - Default
-
None
-
None
-
Not defined
Context:
As discussed as part of this change https://github.com/camunda/camunda-optimize/pull/3320/files#r600443910 instead of having our ElasticSearchJunitExtension set some arbitrary settings on elastic to account for concurrent test execution load we should extract these to the CI environment setup. Ideally we can make reuse of that in jobs using the optimize shared lib for jenkins.
AT:
- cluster settings required due to high test concurrency (maven forks) should be part of the environment setup and not the junit extension