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

[QA][Stack Integration Tests] Support defining the tests list in the Integration Test Repo #83363

Merged
merged 11 commits into from
Dec 4, 2020

Conversation

wayneseymour
Copy link
Member

@wayneseymour wayneseymour commented Nov 13, 2020

Support both in the config.
Consume the state of the TESTS_LIST directly from the state file.

This pr depends on https://github.com/elastic/integration-test/pull/409

…Integration Test repo or Kibana

Support both in the config.
Update fromNullable to include an empty string predicate.
@wayneseymour wayneseymour self-assigned this Nov 13, 2020
@wayneseymour wayneseymour added release_note:skip Skip the PR/issue when compiling release notes v8.0.0 labels Nov 13, 2020
…Integration Test repo or Kibana

Support both in the config.
Update fromNullable to include an empty string predicate.
@apmmachine
Copy link
Contributor

💚 Build Succeeded

…Integration Test repo or Kibana

Split external test list into an array.
@wayneseymour wayneseymour marked this pull request as ready for review November 18, 2020 18:28
@wayneseymour wayneseymour requested a review from a team as a code owner November 18, 2020 18:28
@wayneseymour
Copy link
Member Author

@elasticmachine merge upstream

kibanamachine and others added 3 commits November 18, 2020 13:28
…Integration Test repo

Drop build_state and use consume_state in order to
easily signify that we are using state that's generated elsewhere.
@wayneseymour wayneseymour changed the title [QA][Stack Integration Tests] Support defining the tests list in the Integration Test repo or Kibana [QA][Stack Integration Tests] Support defining the tests list in the Integration Test Repo Nov 18, 2020
@wayneseymour
Copy link
Member Author

@elasticmachine merge upstream

Copy link

@LeeDr LeeDr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@wayneseymour
Copy link
Member Author

@elasticmachine merge upstream

@kibanamachine
Copy link
Contributor

💚 Build Succeeded

Metrics [docs]

✅ unchanged

History

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

@wayneseymour wayneseymour merged commit b6a6a30 into master Dec 4, 2020
@wayneseymour wayneseymour deleted the support-test-list-in-both-repos branch December 4, 2020 21:34
@wayneseymour
Copy link
Member Author

@LeeDr where does this need to be backported to?

@LeeDr LeeDr added the v7.11.0 label Dec 7, 2020
@kibanamachine kibanamachine added the backport missing Added to PRs automatically when the are determined to be missing a backport. label Dec 8, 2020
@kibanamachine
Copy link
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create backports run node scripts/backport --pr 83363 or prevent reminders by adding the backport:skip label.

wayneseymour added a commit to wayneseymour/kibana that referenced this pull request Dec 8, 2020
…Integration Test Repo (elastic#83363)

Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
@kibanamachine kibanamachine removed the backport missing Added to PRs automatically when the are determined to be missing a backport. label Dec 8, 2020
wayneseymour added a commit that referenced this pull request Dec 8, 2020
…n the Integration Test Repo (#83363) (#85334)

Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>

Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release_note:skip Skip the PR/issue when compiling release notes v7.11.0 v8.0.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants