[Security Solution] Integrates security solution tests with Kibana QA quality gate#187266
[Security Solution] Integrates security solution tests with Kibana QA quality gate#187266MadameSheema merged 13 commits intoelastic:mainfrom
Conversation
MadameSheema
added
release_note:skip
|
Pinging @elastic/security-solution (Team: SecuritySolution) |
|
@MadameSheema we're discussing things async. Will come back here once we have a agreement. |
…our QGs (#187389) ## 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: - All the API tests marked as `@serverless` are going to be executed as part of the periodic pipeline - Once this other [PR](#187266) is merged, all the API tests marked as `@serverlessQA` will be executed as part of the Kibana QA QG (second quality gate). --------- Co-authored-by: dkirchan <diamantis.kirchantzoglou@elastic.co>
💚 Build Succeeded
Metrics [docs]
History
|
Co-authored-by: Robert Oskamp <traeluki@gmail.com>
|
@jbudz @pheyos we have a full week of green results on the tests tagged to be executed as part of the kibana QA quality gate |
@lukeelmers is taking lead on approving |
|
I've checked the pipeline and started a slack discussion with @MadameSheema. |
pheyos
left a comment
pheyos
left a comment
There was a problem hiding this comment.
The discussed criteria for the quality gate addition are sufficiently met. There are a few follow-up items on the list, which should be addressed near-term, but this is not blocking here.
| build: | ||
| env: | ||
| ENVIRONMENT: ${ENVIRONMENT} | ||
| message: "${BUILDKITE_MESSAGE} (triggered by pipeline.tests-qa.yaml)" |
💛 Build succeeded, but was flaky
Failed CI StepsMetrics [docs]
History
To update your PR or re-run it, just comment with: |
7 participants
Summary
Once this PR is merged, when the Kibana QA quality gate is triggered the following tests are going to be executed:
@serverlessQA@serverlessQACurrently there are only a few that have been extensively tested and are passing on MKI environments.
The current and future tests:
We have created a run book that has been shared with all the team members of Security Solution and can be found in our internal docs with the title
Security Serverless Kibana QA Quality Gate Failure Run BookSome of the most important points mentioned in the run book:
Below are the channels/groups to be contacted should a test fail:
Detection Engine tests:
Entity Analytics tests:
Explore tests:
Investigations tests:
Gen AI tests:
Rule Management tests:
Defend Workflows tests:
Geneve detection rules tests:
@DomIf nobody responds within 30 minutes: Post the issue in the #security-unified-app channel with the message that team X is not responding and assistance is needed. Tag @sec-eng-prod as well.
Should a failure occur, the Release Manager (RM) will post in the team channell and @ the team responsible. The team, unless in the middle of responding to an SDH Sev1-2, must respond immediately and begin investigation with the RM. Serverless test failures in the Production Quality Release Pipeline are BLOCKING for the entire Kibana Serverless release.