-
Notifications
You must be signed in to change notification settings - Fork 8.3k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[Security Solution][Serverless] Security verify promote es (#188971)
## Summary In this PR, the security FTR tests are added in the [kibana-elasticsearch-serverless-verify-and-promote](https://buildkite.com/elastic/kibana-elasticsearch-serverless-verify-and-promote) In order for this to be done a [new step is added](https://github.com/elastic/kibana/pull/188971/files#diff-c24aca993d6eaa3978eb5334eb5a34d8c7a18a1f5a34b41d43ec9db3e9972a81R67) where only the security FTR + integration tests are running. The reason that I preferred to split the security tests into a different step is the fact that they do not exactly follow the execution way of the rest of the tests in the specific pipeline. They are executed in a different config pattern. We could definitely add the pattern in the existing step like the following way, but I would ask from feedback from the relevant teams for this: `FTR_CONFIG_PATTERNS: "**/test_serverless/**,**/test/security_solution_api_integration/**/serverless.config.ts"` In order for a test to be executed, the test file has mandatorily to be part of the `index.ts` file like [here](https://github.com/elastic/kibana/pull/188971/files#diff-ad4cd826846527b8d18ce4162f5d006723d8ddf6f64a2108528ee7870bd281b0R21). Then in order to add a test or a suite of tests as part of this pipeline a tag needs to be added like [this line](https://github.com/elastic/kibana/pull/188971/files#diff-d166758022907afbfefce03776d6395740408bc65f955549264e7bc9a76087c6R80). --------- Co-authored-by: Brad White <[email protected]> Co-authored-by: Gloria Hornero <[email protected]>
- Loading branch information
1 parent
836af5f
commit 83e78ea
Showing
3 changed files
with
31 additions
and
29 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters