Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add E2E test to check if old registry file can be migrated #11082

Merged
merged 1 commit into from
Apr 16, 2019

Conversation

kvch
Copy link
Contributor

@kvch kvch commented Mar 5, 2019

This PR adds an E2E test to check the functionality of #10504.

Closes #11078

@kvch kvch added the in progress Pull request is currently in progress. label Mar 5, 2019
@kvch kvch force-pushed the test-filebeat-registry-migration branch from 90b93b9 to a76887a Compare March 5, 2019 16:03
@kvch kvch marked this pull request as ready for review March 5, 2019 16:43
@kvch kvch requested a review from a team as a code owner March 5, 2019 16:43
@kvch kvch added review Filebeat Filebeat :Testing and removed in progress Pull request is currently in progress. labels Mar 5, 2019
@kvch kvch requested review from urso and removed request for a team March 5, 2019 16:43
@kvch kvch force-pushed the test-filebeat-registry-migration branch from a76887a to dd08d8d Compare March 6, 2019 12:02
@kvch kvch force-pushed the test-filebeat-registry-migration branch from dd08d8d to a30b1af Compare March 6, 2019 12:03
@kvch
Copy link
Contributor Author

kvch commented Mar 8, 2019

Failing tests are unrelated.

@urso
Copy link

urso commented Apr 15, 2019

@kvch I think you can merge this.

@kvch kvch merged commit 8f8db1a into elastic:master Apr 16, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add E2E test for registry format changes
2 participants