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

[Security Solution] Specific Cypress executions for Entity Analytics team #173024

Merged
merged 7 commits into from
Dec 11, 2023

Conversation

MadameSheema
Copy link
Member

@MadameSheema MadameSheema commented Dec 11, 2023

Summary

This PR is part of the effort we are making to have our cypres serverless tests ready for the second quality gate (QA environment - real serverless project and also part of the initial effort started by #153664.

With the introduced changes, we are creating specific Entity Analytics executions for both ESS and serverless with the aim of:

  • To help to identify quickly the ownership of the tests in case of failure.
  • To help to raise specific flakiness inside the tests of the team.

In this PR:

  • We are creating different executions for ESS, serverless and the quality gate
  • We are integrating everything with buildkite and also adding the new executions to the flaky test suite runner
  • We are updating the readme
  • We are removing the overall Security Solution execution.

@MadameSheema
Copy link
Member Author

/ci

@MadameSheema MadameSheema changed the title moving tests under entity analytics folder [Security Solution] Specific Cypress executions for Entity Analytics team Dec 11, 2023
@MadameSheema MadameSheema marked this pull request as ready for review December 11, 2023 14:23
@MadameSheema MadameSheema requested review from a team as code owners December 11, 2023 14:23
@MadameSheema MadameSheema self-assigned this Dec 11, 2023
@MadameSheema MadameSheema added release_note:skip Skip the PR/issue when compiling release notes Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. v8.12.0 Team:Entity Analytics Security Entity Analytics Team v8.13.0 labels Dec 11, 2023
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-solution (Team: SecuritySolution)

Copy link
Contributor

@hop-dev hop-dev left a comment

Choose a reason for hiding this comment

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

EA changes LGTM, thanks for this! 🚀

Copy link
Contributor

@semd semd left a comment

Choose a reason for hiding this comment

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

LGTM

@MadameSheema MadameSheema enabled auto-merge (squash) December 11, 2023 14:42
@kibana-ci
Copy link
Collaborator

💛 Build succeeded, but was flaky

Failed CI Steps

Metrics [docs]

✅ unchanged

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

cc @MadameSheema

@MadameSheema MadameSheema merged commit 4e6f2cd into elastic:main Dec 11, 2023
51 checks passed
@kibanamachine
Copy link
Contributor

💔 All backports failed

Status Branch Result
8.12 Backport failed because of merge conflicts

You might need to backport the following PRs to 8.12:
- Align inference pipeline card/option styling (#172952)

Manual backport

To create the backport manually run:

node scripts/backport --pr 173024

Questions ?

Please refer to the Backport tool documentation

@kibanamachine kibanamachine added the backport missing Added to PRs automatically when the are determined to be missing a backport. label Dec 13, 2023
@kibanamachine
Copy link
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add the label auto-backport or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 173024 locally

2 similar comments
@kibanamachine
Copy link
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add the label auto-backport or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 173024 locally

@kibanamachine
Copy link
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add the label auto-backport or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 173024 locally

@kibanamachine
Copy link
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add the label auto-backport or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 173024 locally

1 similar comment
@kibanamachine
Copy link
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add the label auto-backport or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 173024 locally

@jaredburgettelastic jaredburgettelastic added the backport:skip This commit does not require backporting label Dec 26, 2023
@kibanamachine kibanamachine removed the backport missing Added to PRs automatically when the are determined to be missing a backport. label Dec 26, 2023
@MadameSheema MadameSheema deleted the entity-analytics-execution branch June 28, 2024 10:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport:skip This commit does not require backporting release_note:skip Skip the PR/issue when compiling release notes Team:Entity Analytics Security Entity Analytics Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. v8.12.0 v8.13.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants