-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[APM] Enable APM integration e2e tests #125724
[APM] Enable APM integration e2e tests #125724
Conversation
…des/kibana into apm-fleet-apm-integration-e2e
@elasticmachine merge upstream |
Pinging @elastic/apm-ui (Team:apm) |
@elasticmachine merge upstream |
💛 Build succeeded, but was flakyTest FailuresMetrics [docs]
History
To update your PR or re-run it, just comment with: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sweet! Thanks for doing this @cauemarcondes
💔 Backport failedThe pull request could not be backported due to the following error: How to fixRe-run the backport manually:
Questions ?Please refer to the Backport tool documentation |
Friendly reminder: Looks like this PR hasn’t been backported yet. |
1 similar comment
Friendly reminder: Looks like this PR hasn’t been backported yet. |
@cauemarcondes do you think this should be added on 8.1.0?. We could also add a |
Thanks @gbamparop I added it. |
* removing package registry docker * unused imports * not used * fixing ts Co-authored-by: Kibana Machine <[email protected]>
We no longer need to spin up the package registry alongside our FTR. Fleet has already implemented a workaround for when it is not available, so for us will be a matter of starting writing the tests.