You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 PR enables the FTR to load a custom "journey" format config file (example). This config file format is a big iteration on the FTR config file format, but using the @kbn/journeys package can be converted into the components necessary for journeys to behave like standard FTR configs, meaning that journeys can be defined cleanly and in a focused way without making major changes to the FTR or creating a new test runner.
In addition to improving the ergonomics of journeys this PR ensures that failed steps trigger failures, something that wasn't happening before. This requires that journeys are very stable, so the stability of existing journeys was improved and debugging was improved in this PR by adding screenshots taken at the end of each step to failure reports and ensuring that these reports are uploaded in hourly SUPT jobs (example)
Sorry about that @dmlemeshko, my migration of the config file to not need the removed base.config.js file wasn't good, looks like I've got it working now though.
Total count of every public API that lacks a comment. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats comments for more detailed information.
Total count of every any typed public API. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats any for more detailed information.
Total count of every type that is part of your API that should be exported but is not. This will cause broken links in the API documentation system. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats exports for more detailed information.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #140676
This PR enables the FTR to load a custom "journey" format config file (example). This config file format is a big iteration on the FTR config file format, but using the
@kbn/journeys
package can be converted into the components necessary for journeys to behave like standard FTR configs, meaning that journeys can be defined cleanly and in a focused way without making major changes to the FTR or creating a new test runner.For a comprehensive example of how journeys look in this new format, checkout x-pack/performance/journeys/web_logs_dashboard.ts.
In addition to improving the ergonomics of journeys this PR ensures that failed steps trigger failures, something that wasn't happening before. This requires that journeys are very stable, so the stability of existing journeys was improved and debugging was improved in this PR by adding screenshots taken at the end of each step to failure reports and ensuring that these reports are uploaded in hourly SUPT jobs (example)
Verified changes to performance pipeline in https://buildkite.com/elastic/kibana-pull-request/builds/72898