Dzmitry Lemechko
50393be0a8
[ci] retry scalability testing step on failure ( #149399 )
...
## Summary
Quite often bootstrap
[fails](https://buildkite.com/elastic/kibana-scalability-benchmarking/builds/957#0185e31d-dcc8-42f4-ac3a-e0399a175519 )
on `kb-static-scalability-01` bare metal machine:
<details>
<summary>Bootstrap failure: [bazel] exited with code [1]</summary>
```
$ node scripts/kbn bootstrap
| 2023-01-24 11:00:50 CEST | HINT
| 2023-01-24 11:03:31 CEST | HINT If experiencing problems with node_modules try `yarn kbn bootstrap --force-install` or as last resort `yarn kbn reset && yarn kbn bootstrap`
| 2023-01-24 11:03:31 CEST | HINT
| 2023-01-24 11:03:31 CEST | ERROR [bootstrap] failed: [bazel] exited with code [1]
| 2023-01-24 11:03:31 CEST | output:
| 2023-01-24 11:03:31 CEST | INFO: Invocation ID: 207c041d-23b8-4f07-bf56-8cb961819546
| 2023-01-24 11:03:31 CEST |
| 2023-01-24 11:03:31 CEST | <--- Last few GCs --->
| 2023-01-24 11:03:31 CEST |
| 2023-01-24 11:03:31 CEST | [1304562:0x74b83a0] 154462 ms: Mark-sweep 4023.8 (4130.2) -> 4011.3 (4131.0) MB, 1677.3 / 0.0 ms (average mu = 0.149, current mu = 0.074) task; scavenge might not succeed
| 2023-01-24 11:03:31 CEST | [1304562:0x74b83a0] 155522 ms: Mark-sweep 4024.7 (4131.0) -> 4012.0 (4131.7) MB, 924.0 / 0.0 ms (average mu = 0.142, current mu = 0.128) task; scavenge might not succeed
| 2023-01-24 11:03:31 CEST |
| 2023-01-24 11:03:31 CEST |
| 2023-01-24 11:03:31 CEST | <--- JS stacktrace --->
| 2023-01-24 11:03:31 CEST |
| 2023-01-24 11:03:31 CEST | FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
| 2023-01-24 11:03:31 CEST | 1: 0xb6b850 node::Abort() [/var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/fbd7d220b25178fcebe6b4ba126fca45/external/nodejs_linux_amd64/bin/nodejs/bin/node]
| 2023-01-24 11:03:31 CEST | 2: 0xa806a6 [/var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/fbd7d220b25178fcebe6b4ba126fca45/external/nodejs_linux_amd64/bin/nodejs/bin/node]
| 2023-01-24 11:03:31 CEST | 3: 0xd52140 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [/var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/fbd7d220b25178fcebe6b4ba126fca45/external/nodejs_linux_amd64/bin/nodejs/bin/node]
| 2023-01-24 11:03:31 CEST | 4: 0xd524e7 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [/var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/fbd7d220b25178fcebe6b4ba126fca45/external/nodejs_linux_amd64/bin/nodejs/bin/node]
| 2023-01-24 11:03:31 CEST | 5: 0xf2fbe5 [/var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/fbd7d220b25178fcebe6b4ba126fca45/external/nodejs_linux_amd64/bin/nodejs/bin/node]
| 2023-01-24 11:03:31 CEST | 6: 0xf30ae8 v8::internal::Heap::RecomputeLimits(v8::internal::GarbageCollector) [/var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/fbd7d220b25178fcebe6b4ba126fca45/external/nodejs_linux_amd64/bin/nodejs/bin/node]
| 2023-01-24 11:03:31 CEST | 7: 0xf40ff3 [/var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/fbd7d220b25178fcebe6b4ba126fca45/external/nodejs_linux_amd64/bin/nodejs/bin/node]
| 2023-01-24 11:03:31 CEST | 8: 0xf41e68 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/fbd7d220b25178fcebe6b4ba126fca45/external/nodejs_linux_amd64/bin/nodejs/bin/node]
| 2023-01-24 11:03:31 CEST | 9: 0xfb1124 v8::internal::ScavengeJob::Task::RunInternal() [/var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/fbd7d220b25178fcebe6b4ba126fca45/external/nodejs_linux_amd64/bin/nodejs/bin/node]
| 2023-01-24 11:03:31 CEST | 10: 0xe2187b non-virtual thunk to v8::internal::CancelableTask::Run() [/var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/fbd7d220b25178fcebe6b4ba126fca45/external/nodejs_linux_amd64/bin/nodejs/bin/node]
| 2023-01-24 11:03:31 CEST | 11: 0xbd6684 [/var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/fbd7d220b25178fcebe6b4ba126fca45/external/nodejs_linux_amd64/bin/nodejs/bin/node]
| 2023-01-24 11:03:31 CEST | 12: 0xbd9aee node::PerIsolatePlatformData::FlushForegroundTasksInternal() [/var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/fbd7d220b25178fcebe6b4ba126fca45/external/nodejs_linux_amd64/bin/nodejs/bin/node]
| 2023-01-24 11:03:31 CEST | 13: 0x1652906 [/var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/fbd7d220b25178fcebe6b4ba126fca45/external/nodejs_linux_amd64/bin/nodejs/bin/node]
| 2023-01-24 11:03:31 CEST | 14: 0x1664e44 [/var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/fbd7d220b25178fcebe6b4ba126fca45/external/nodejs_linux_amd64/bin/nodejs/bin/node]
| 2023-01-24 11:03:31 CEST | 15: 0x165326e uv_run [/var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/fbd7d220b25178fcebe6b4ba126fca45/external/nodejs_linux_amd64/bin/nodejs/bin/node]
| 2023-01-24 11:03:31 CEST | 16: 0xaafa2d node::SpinEventLoop(node::Environment*) [/var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/fbd7d220b25178fcebe6b4ba126fca45/external/nodejs_linux_amd64/bin/nodejs/bin/node]
| 2023-01-24 11:03:31 CEST | 17: 0xbb11f4 node::NodeMainInstance::Run() [/var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/fbd7d220b25178fcebe6b4ba126fca45/external/nodejs_linux_amd64/bin/nodejs/bin/node]
| 2023-01-24 11:03:31 CEST | 18: 0xb26c44 node::LoadSnapshotDataAndRun(node::SnapshotData const**, node::InitializationResult const*) [/var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/fbd7d220b25178fcebe6b4ba126fca45/external/nodejs_linux_amd64/bin/nodejs/bin/node]
| 2023-01-24 11:03:31 CEST | 19: 0xb2a83f node::Start(int, char**) [/var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/fbd7d220b25178fcebe6b4ba126fca45/external/nodejs_linux_amd64/bin/nodejs/bin/node]
| 2023-01-24 11:03:31 CEST | 20: 0x7fbc908be083 __libc_start_main [/lib/x86_64-linux-gnu/libc.so.6]
| 2023-01-24 11:03:31 CEST | 21: 0xaad7ee _start [/var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/fbd7d220b25178fcebe6b4ba126fca45/external/nodejs_linux_amd64/bin/nodejs/bin/node]
| 2023-01-24 11:03:31 CEST | /var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/fbd7d220b25178fcebe6b4ba126fca45/external/nodejs_linux_amd64/bin/yarn: line 19: 1304562
2023-01-26 16:02:23 +01:00
Jon
e8ceb4ed49
[ci/on-merge] Trigger container image build ( #149350 )
...
Reopens #148864 to trigger via REST instead of yaml. The previous
implementation did not support commit triggered builds.
This conditionally adds a pipeline trigger to
`kibana-artifacts-container-image` at the end of the on-merge pipeline
when tests are passing. The triggered pipeline will build (and
eventually push) our default docker images.
2023-01-23 13:16:56 -07:00
Jonathan Budzenski
ece7b8ffdf
Revert "[ci/on-merge] Trigger container image build ( #148864 )"
...
This reverts commit 8dff4b1881
2023-01-19 17:51:57 -06:00
Jon
8dff4b1881
[ci/on-merge] Trigger container image build ( #148864 )
...
This conditionally adds a pipeline trigger to
`kibana-artifacts-container-image` at the end of the on-merge pipeline
when tests are passing. The triggered pipeline will build (and
eventually push) our default docker images.
Tests passing -> image build:
https://buildkite.com/elastic/kibana-on-merge/builds/25854
Tests failing -> no image build:
https://buildkite.com/elastic/kibana-on-merge/builds/25849
2023-01-19 16:43:01 -06:00
Dzmitry Lemechko
a94a1b620e
[performance] Disable telemetry for journey by default ( #148915 )
...
## Summary
I noticed some noise in [Performance
dashboard](dd0473achttps://buildkite.com/elastic/kibana-performance-data-set-extraction ))
running on regular workers or local troubleshooting there is no much
value to collect inconsistent values.
2023-01-13 23:50:14 +01:00
Jon
ecadc4a20a
[ci] Add build scripts for latest docker image ( #148606 )
...
This adds a new pipeline to build our default container image, using the
`kibana-ci` docker namespace and the docker version based on the first 7
digits of the commit hash.
https://buildkite.com/elastic/kibana-artifacts-container-image/builds/3
Will have followups for:
1) on-merge trigger
2) docker push / controller pipeline trigger
need to make sure branches other than main, and manual triggers
(untested) skip publishing.
2023-01-13 13:46:40 -06:00
Dzmitry Lemechko
bc2cb5dc61
[code coverage] removing instrumentation & plugin for functional tests ( #148748 )
...
## Summary
Quite awhile ago we decided to stop collecting code coverage for our
functional (e2e, api integration) FTR tests.
This is a cleanup PR to remove the code we no longer use.
### Checklist
Delete any items that are not applicable to this PR.
- [ ] Any text added follows [EUI's writing
guidelines](https://elastic.github.io/eui/#/guidelines/writing ), uses
sentence case text and includes [i18n
support](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md )
- [ ]
[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html )
was added for features that require explanation or tutorials
- [ ] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html )
were updated or added to match the most common scenarios
- [ ] Any UI touched in this PR is usable by keyboard only (learn more
about [keyboard accessibility](https://webaim.org/techniques/keyboard/ ))
- [ ] Any UI touched in this PR does not create any new axe failures
(run axe in browser:
[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/ ),
[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US ))
- [ ] If a plugin configuration key changed, check if it needs to be
allowlisted in the cloud and added to the [docker
list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker )
- [ ] This renders correctly on smaller devices using a responsive
layout. (You can test this [in your
browser](https://www.browserstack.com/guide/responsive-testing-on-local-server ))
- [ ] This was checked for [cross-browser
compatibility](https://www.elastic.co/support/matrix#matrix_browsers )
### Risk Matrix
Delete this section if it is not applicable to this PR.
Before closing this PR, invite QA, stakeholders, and other developers to
identify risks that should be tested prior to the change/feature
release.
When forming the risk matrix, consider some of the following examples
and how they may potentially impact the change:
| Risk | Probability | Severity | Mitigation/Notes |
|---------------------------|-------------|----------|-------------------------|
| Multiple Spaces—unexpected behavior in non-default Kibana Space.
| Low | High | Integration tests will verify that all features are still
supported in non-default Kibana Space and when user switches between
spaces. |
| Multiple nodes—Elasticsearch polling might have race conditions
when multiple Kibana nodes are polling for the same tasks. | High | Low
| Tasks are idempotent, so executing them multiple times will not result
in logical error, but will degrade performance. To test for this case we
add plenty of unit tests around this logic and document manual testing
procedure. |
| Code should gracefully handle cases when feature X or plugin Y are
disabled. | Medium | High | Unit tests will verify that any feature flag
or plugin combination still results in our service operational. |
| [See more potential risk
examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx ) |
### For maintainers
- [ ] This was checked for breaking API changes and was [labeled
appropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process )
2023-01-12 16:44:48 +01:00
Spencer
8e6f155e0c
support disabling kibana build download in functional/common.sh ( #148461 )
...
We need to disable downloading the Kibana build for steps which don't
need it, especially in builds which skip building Kibana completely
2023-01-05 10:41:28 -07:00
Spencer
2adf37b203
[fleet/pkgsDaily] disable CI log capture so we can see logging on success ( #148459 )
2023-01-05 08:21:54 -07:00
Patryk Kopyciński
c0d2a032f9
[Defend Workflows] Init Cypress ( #147822 )
...
## Summary
Add initial Cypress pipeline for Defend Workflows Team
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
Co-authored-by: Ashokaditya <1849116+ashokaditya@users.noreply.github.com>
2023-01-04 17:05:13 +01:00
Shahzad
af7dd7fc56
[Synthetics] Custom reporter for e2e testing ( #148251 )
2023-01-04 08:25:44 +01:00
Giorgos Bamparopoulos
042403e606
[APM] Add parallel builds for cypress tests ( #142598 )
...
- Tests runs initiated by the flaky test runner are not recorded or
parallelized
2022-12-21 15:36:08 +00:00
Jonathan Budzenski
26a1a926c3
[ci/cypress] Use spot instances ( #147196 )
...
This migrates the remaining ci-group-6 steps to n2-4-spot.
2022-12-12 14:28:03 -06:00
Thomas Watson
39d27bb868
Add custom Buildkite pipeline for @kbn/handlebars ( #146964 )
...
Closes #146963
2022-12-08 18:28:33 +01:00
Dzmitry Lemechko
852299b535
[performance] add APM data set extraction pipeline ( #147177 )
...
## Summary
Part of #140828
PR for run yml file
[elastic/kibana-buildkite/pull/67](https://github.com/elastic/kibana-buildkite/pull/67 )
This PR moves data set extraction step in separate pipeline, still
reporting KIbana scalability and ES Rally output in Kibana-related
bucket.
Reporting ES Rally data to required bucket will be added in the
follow-up PR.
2022-12-07 19:02:15 +01:00
Luke Gmys
f1be6057c8
[TIP] Run e2e pipeline on CI ( #144776 )
...
## Summary
Last week, our team has dicovered that e2e tests are not executed on CI,
this PR is an attempt to fix that.
Threat intel pipeline should be run whenever the `threat_intelligence`
plugin source or related tests config has changed.
2022-11-09 12:51:09 +01:00
Jonathan Budzenski
62c62c3c2c
[ci] Set elasticsearch snapshot build timeout ( #144831 )
...
We had a few stalled builds that timed out after 1d. Successful builds
typically take 15m-18m. This sets the timeout 30 minutes.
2022-11-08 12:07:37 -06:00
Tiago Costa
3dd5c5388e
chore(NA): update ci step name to Check Public API Docs ( #144573 )
...
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
2022-11-04 02:27:23 +00:00
Jonathan Budzenski
f1f2107584
[ci/cloud-deploy] Remove CI success requirement ( #141965 )
...
This removes the success requirement in the cloud deployment step for
pull requests.
Creating a cloud deployment from a pull request is optional and not
providing test coverage. Failures are typically upstream and not
something that can be fixed from the Kibana repository.
2022-10-05 11:43:15 -05:00
Spencer
249b596465
[journeys] restart ES for each journey, fix flakiness ( #141530 )
2022-09-26 08:56:31 -07:00
Spencer
50b3b57d9e
[ftr] add first-class support for playwrite journeys ( #140680 )
...
* [ftr] add first-class support for playwrite journeys
* [CI] Auto-commit changed files from 'node scripts/generate codeowners'
* fix jest test
* remove ability to customize kibana server args, if we need it we can add it back
* remove dev dir that doesn't exist
* fix typo
* prevent duplicated array converstion logic by sharing flag reader
* remove destructuring of option
* fix scalability config and config_path import
* fix start_servers args and tests
* include simple readme
* fix jest tests and support build re-use when changes are just to jest tests
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
2022-09-22 01:06:46 -07:00
Tyler Smalley
7be5ac42a0
[artifacts/cft] Soft fail on timeout ( #141180 )
...
Co-authored-by: Jonathan Budzenski <jon@elastic.co>
2022-09-21 09:32:36 -05:00
Tyler Smalley
7cc3e68e10
Revert "[cft] Soft fail on timeout ( #141165 )"
...
This reverts commit 2d0d3a58f2
2022-09-20 14:02:07 -07:00
Jonathan Budzenski
2d0d3a58f2
[cft] Soft fail on timeout ( #141165 )
2022-09-20 15:49:27 -05:00
Jonathan Budzenski
874e4cb913
[artifacts] Improve cloud deployment error handling ( #137775 )
...
* [artifacts] Improve cloud deployment error handling
* Update .buildkite/scripts/steps/artifacts/cloud.sh
Co-authored-by: Spencer <spencer@elastic.co>
* update retry codes
Co-authored-by: Spencer <spencer@elastic.co>
2022-09-06 12:43:40 -05:00
Dzmitry Lemechko
f0fe485e7d
Add pipeline to run scalability tests from APM traces ( #139548 )
...
* add scalability pipeline to run scenarios from APM traces
* update runner description
* remove retry-all-errors curl flag
* add flag for curl to ignore connection refused
* override ES_HOST for gatling runner
* exclude config from regular CI, remove bail flag
* fix uploaded scalability traces
* fix text and remove space
* add validation in config
* use functions instead of scripts
* renaming var in loop
* add step timeout
* define functions before call
* use trap for stopping ES
* fix path for artifacts extraction
* update serverArgs
* add pre-build step
* add pre-build step
* use default pre-build step
* delete step
* print BUILDKITE_PIPELINE_SLUG
* disable telemetry
* remove log
* enable telemetry
* add step to upload test results
* move trap after pid
* upload test reports to gcs
* fix script
* Revert "fix script"
This reverts commit 1c6bc3f45cc957a31c32
2022-09-05 18:30:44 +02:00
Dzmitry Lemechko
a9ab0bf351
[performance pipeline] 60 min timeout for test step ( #139613 )
2022-08-29 15:39:01 +02:00
Spencer
a16fd1e033
[perf-tests/scalability] improve logging when uploading traces ( #139477 )
...
* [perf-tests/scalability] improve logging when uploading traces
* restore including kibana artifacts in scalability dataset
* create parent dirs too
* support skipping builds too
2022-08-26 20:09:04 +02:00
Jonathan Budzenski
a2f3e3bd7c
Bump linux bazel cache timeout to 30 minutes ( #139491 )
...
We're seeing some timeouts recently in the 15 minute range.
Mac timeouts are already at 60 min.
2022-08-25 11:11:11 -05:00
Brian Seeders
1019295b09
[CI] Improve reliability of macos bazel cache jobs ( #138554 )
2022-08-10 13:11:59 -07:00
Brian Seeders
4f100c4ed0
[CI] Convert the remaining steps in primary pipelines to spot instances ( #138168 )
2022-08-09 16:16:39 -04:00
Spencer
92fb5dbafc
[ci] mark PR stats as usable for metrics ( #138297 )
2022-08-08 14:12:04 -07:00
Jonathan Budzenski
22b21645bb
[ci] Conditional storybook builds ( #136219 )
...
* [ci] Conditional storybook builds
This moves storybook builds to run conditionally, either if there's a
storybook change or the `ci:build-storybooks` label is set.
These builds don't seem to be providing test coverage, and may not be utilized
in scenarios such as automated backports or unrelated changes.
* test regex
* formatting
* Revert "test regex"
This reverts commit dcef465414
2022-08-02 11:24:01 -05:00
Brian Seeders
20dec08bf1
[CI] Parallelize eslint to speed it up ( #136972 )
2022-07-22 16:23:17 -04:00
Jonathan Budzenski
1410bc4aa5
[cft] Add pipeline to shutdown deployment ( #136659 )
...
* [cft] Add pipeline to shutdown deployment
* 755
* save file
2022-07-20 10:22:25 -05:00
Dzmitry Lemechko
b72601c283
[performance] Re-enable apm extraction step ( #136555 )
...
* [kbn-performance-testing-dataset-extractor] add extra logging
* re-enable step
2022-07-19 09:35:54 +02:00
Jonathan Budzenski
b5b735625c
[cft] Use spot instance ( #135742 )
...
* [cft] Use spot instance, increase cpu
* revert back to n2
* Update .buildkite/pipelines/pull_request/deploy_cloud.yml
Co-authored-by: Tyler Smalley <tylersmalley@gmail.com>
Co-authored-by: Tyler Smalley <tylersmalley@gmail.com>
2022-07-12 14:55:50 -05:00
Jonathan Budzenski
8acc1466f8
[ci] Conditonal webpack bundle reports ( #136215 )
...
* [ci] Conditonal webpack bundle reports
* fix
* spacing
* \n
* fix file path
2022-07-12 12:30:49 -05:00
Baturalp Gurdin
d83f802099
stop scalability step in performance pipeline ( #136211 )
...
Co-authored-by: Spencer <spencer@elastic.co>
2022-07-12 09:14:18 -07:00
Jonathan Budzenski
87ac0fd2fe
[docker] Add ubi9 image ( #135868 )
...
* [docker] Add ubi9 image
* update artifacts tests
* cleanup
* fixes
* formatting
2022-07-08 12:02:59 -05:00
spalger
7731c414db
[ci] build webpack bundle repotrs on a larger machine
...
We've seen OOMs on this recently, to prevent blocking more people we're just going to bump the instance size until we can narrow down the problem.
2022-07-08 08:44:00 -05:00
Spencer
9619311120
[ci] fix ftr script when called with parallelism ( #135713 )
...
* fix ftr script when called with parallelism
* Update ftr_configs.sh
2022-07-05 09:14:26 -05:00
Brian Seeders
0b0b68786a
[CI] Move kibana-buildkite-library into kibana ( #134787 )
2022-06-28 13:19:05 -04:00
Shahzad
d6f2dc1042
[Exploratory view] Add e2e tests ( #135148 )
...
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
2022-06-28 13:31:12 +02:00
Dzmitry Lemechko
d86f977884
[performance] re-enable scalability dataset extraction step on CI ( #134719 )
...
* add scalability setup for login and promotion_tracking_dashboard journeys, re-enable step on ci
* update query to get single ftr transaction
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
2022-06-24 16:18:41 +02:00
Tre
85dc5b3578
[QA][Code Coverage] Add meta data links ci runs. ( #134731 )
...
* [QA][Code Coverage] Add a link to discover pinned to the current build.
When personnel other than myself wish to visually verify code coverage,
this link will be available in the ci output.
* Drop single quotes.
* Add annotation per J Budz.
* Fixup text.
* Drop debug.
2022-06-23 16:00:48 +01:00
Baturalp Gurdin
e5d73a1169
ingest performance metrics to ci-stats ( #134792 )
2022-06-22 15:44:11 -07:00
Vitalii Dmyterko
746e259733
[Security Solution] fixes flaky-test-runner Cypress Security Solution tests ( #134205 )
...
## Summary
Fixes issue with security solution cypress flaky test runner
After introducing [dynamic split for cypress tests in Security Solution](https://github.com/elastic/kibana/pull/125986 ), there was discovered an issue with flaky test runner, which is using parallelism in slightly different manner: https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/697#_ : tests were evenly split between N jobs, instead of repeating tests N times(as N jobs)
So, for flaky runner, I introducing a new ENV variable that would disable split for tests between parallel jobs and instead would run all test per each job.
Here is link to flaky runner build from this PR, which shows that all test runs per job
https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/736
2022-06-16 09:29:17 +01:00
Brian Seeders
b32052e66a
[CI] Trigger pipeline deploy when versions.json changes ( #134387 )
2022-06-15 10:47:35 -04:00
Kibana Machine
0cb1087fb4
[api-docs] 2022-06-14 Daily api_docs build ( #134389 )
...
* [api-docs] Add pipeline to build api_docs daily
* Fix kibanamachine remote
* Add --repo
* Fix PR creation
* [api-docs] Daily api_docs build
Co-authored-by: Brian Seeders <brian.seeders@elastic.co>
2022-06-14 12:58:55 -07:00
