[
https://issues.apache.org/jira/browse/UNOMI-531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17445944#comment-17445944
]
Serge Huber commented on UNOMI-531:
-----------------------------------
Currently the integration tests launched their own ElasticSearch instance using
a Maven plugin. There is already a Maven property attached to this:
{code}
<groupId>com.github.alexcojocaru</groupId>
<artifactId>elasticsearch-maven-plugin</artifactId>
<!-- REPLACE THE FOLLOWING WITH THE PLUGIN VERSION YOU
NEED -->
<version>6.19</version>
<configuration>
<clusterName>contextElasticSearchITests</clusterName>
<transportPort>9500</transportPort>
<httpPort>9400</httpPort>
<version>${elasticsearch.version}</version>
{code}
So we could just test using something like:
mvn clean install -P integration-tests -Delasticsearch.version=7.14.1
> Update the integration tests to support running on different versions of
> Elasticsearch
> --------------------------------------------------------------------------------------
>
> Key: UNOMI-531
> URL: https://issues.apache.org/jira/browse/UNOMI-531
> Project: Apache Unomi
> Issue Type: Task
> Reporter: Francois Gerthoffert
> Priority: Major
> Fix For: 2.0.0, 1.6.0
>
>
> The objective of this ticket is to be able to run the integration tests on
> any version of Elasticsearch by providing the corresponding variable to the
> framework.
> This would be triggered similarly to what is being done today in the GitHub
> action for Java versions:
> {code:java}
> strategy:
> matrix:
> java: [ 1.8, 11] {code}
> We would then be running these tests regularly on the minimum supported
> version (currently 7.4.2) and on any "latest" released version.
> It would be best if we could test not only the elasticsearch version, but
> also compatible forks (such as Opensearch).
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
