Skip to content

Conversation

@jimczi
Copy link
Contributor

@jimczi jimczi commented Apr 23, 2019

This commit adapts the rolling upgrade test introduced in #37808
to ignore runs that upgrade from a version on or after 7.0
Since it is not possible to check the upgrade version in the yml test this change introduces a new AbstractRollingTestCase that extracts the version from a system property.
The previous test has been removed (a69e104) from this branch to avoid this problem but it is now failing on the 7.0 branch since the creation of 7.0.1.

Closes #41453

This commit adapts the rolling upgrade test introduced in elastic#37808
to ignore runs that upgrade from a version on or after 7.0.

Closes elastic#41453
@jimczi jimczi added >non-issue :Search Foundations/Mapping Index mappings, including merging and defining field types >test-failure Triaged test failures from CI v7.2.0 labels Apr 23, 2019
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-search

@jimczi jimczi added the v7.0.1 label Apr 23, 2019
@jaymode jaymode added v7.0.2 and removed v7.0.1 labels Apr 24, 2019
@jimczi jimczi requested a review from jpountz April 26, 2019 08:28
@jimczi jimczi merged commit a8c3c5c into elastic:7.x Apr 27, 2019
@jimczi jimczi deleted the upgrade/all_field branch April 27, 2019 16:37
jimczi added a commit that referenced this pull request Apr 27, 2019
This commit adapts the rolling upgrade test introduced in #37808
to ignore runs that upgrade from a version on or after 7.0.

Closes #41453
@jaymode jaymode added v7.0.1 and removed v7.0.2 labels Apr 29, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

>non-issue :Search Foundations/Mapping Index mappings, including merging and defining field types >test-failure Triaged test failures from CI v7.0.1 v7.2.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants