-
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
[Security Solution][Threat Hunting] Adds threat hunting API tests to our QGs #187389
Conversation
Pinging @elastic/security-solution (Team: SecuritySolution) |
Pinging @elastic/security-threat-hunting (Team:Threat Hunting) |
Pinging @elastic/security-threat-hunting-explore (Team:Threat Hunting:Explore) |
Pinging @elastic/security-threat-hunting-investigations (Team:Threat Hunting:Investigations) |
- exit_status: "1" | ||
limit: 2 | ||
|
||
steps: |
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.
steps here introduce a duplicate key. I dont know if it will be working. Remove steps line as it is mentioned above.
💛 Build succeeded, but was flaky
Failed CI StepsMetrics [docs]
History
|
Summary
The Threat Hunting API tests are not part of our QGs, in this PR we are adding them to it.
Once this PR is merged:
@serverless
are going to be executed as part of the periodic pipeline@serverlessQA
will be executed as part of the Kibana QA QG (second quality gate).