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

ci(jenkins): use e2e in the CI #61803

Merged
merged 111 commits into from
May 26, 2020
Merged

ci(jenkins): use e2e in the CI #61803

merged 111 commits into from
May 26, 2020

Conversation

v1v
Copy link
Member

@v1v v1v commented Mar 30, 2020

Changes

  • Increase the timeout in the user inspects the opbeans-node service action.
  • Fix wait-for and some minor changes in the bash script.
  • Create wrappers to prepare the CI context and run the e2e script.
  • Delete the CI scripts that were used previously to use docker instead.
  • Pipeline stages are just two, prepare the Kibana app and run the e2e script.
  • Update docs.
  • Workaround [Platform] Status endpoint incorrectly returns 200 before Kibana is ready #66326

Related issues

Supersedes #58213
Closes #62979
Workaround #66326

Actions

  • Wait for the APM-UI team to get what's the Kibana startup command to be used rather than running the tests a few times to warm up the Kibana instance.
  • Recent changes in the upstream makes the e2e fail in the CI, for instance the merge from master did work successfully, but the following ones didn't work.

image

Screenshot with the error

image

then we don't need to trap the errorlevel
… watch

failed to watch files Error: ENOSPC: System limit for number of file watchers reached, watch '/var/lib/jenkins/workspace/ui_apm-ui-e2e-tests-mbp_PR-58213/src/github.com/elastic/kibana/x-pack/legacy/plugins/siem/server/lib/detection_engine/rules/prepackaged_rules/windows_defense_evasion_via_filter_manager.json
@v1v
Copy link
Member Author

v1v commented May 26, 2020

jenkins run the e2e

Copy link
Member

@sorenlouv sorenlouv left a comment

Choose a reason for hiding this comment

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

Beautiful!

@kibanamachine
Copy link
Contributor

💚 Build Succeeded

History

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

@v1v v1v merged commit abcee09 into elastic:master May 26, 2020
@v1v v1v deleted the feature/e2e-changes branch May 26, 2020 15:18
@kibanamachine kibanamachine added the backport missing Added to PRs automatically when the are determined to be missing a backport. label May 27, 2020
@kibanamachine
Copy link
Contributor

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

2 similar comments
@kibanamachine
Copy link
Contributor

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

@kibanamachine
Copy link
Contributor

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

@v1v v1v added backport:skip This commit does not require backporting and removed backport missing Added to PRs automatically when the are determined to be missing a backport. labels May 29, 2020
@v1v v1v removed the [zube]: Done label Jun 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automation backport:skip This commit does not require backporting release_note:skip Skip the PR/issue when compiling release notes Team:APM All issues that need APM UI Team support
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[APM] e2e ingest data is failing randomly
7 participants