mirror of
https://github.com/elastic/kibana.git
synced 2025-04-21 16:29:04 -04:00
16f69b7b2d
## Summary After a CI run, Storybooks are built. Each commit is built and uploaded separately, which makes sense: https://github.com/elastic/kibana/blob/main/.buildkite/scripts/steps/storybooks/build_and_upload.ts#L24 Unfortunately, we don't have a way to consistently point to main, or to a PR. ## PRs Using https://github.com/elastic/kibana/pull/206540 as an example, the Storybook is currently hosted at: https://ci-artifacts.kibana.dev/storybooks/pr-206540/803ec26fb200e1fd23c33ead174dcc5356262cfc This means that, if I push another commit, the URL will change... so all of the links I've posted in Slack are now invalid. This PR changes the URL so it will remain: https://ci-artifacts.kibana.dev/storybooks/pr-206540 regardless of how many commits I push. ## `main` Furthermore, being able to visit https://ci-artifacts.kibana.dev/storybooks/main/latest/index.html to see the most recent Storybook build is awesome. The issue is each Storybook is hosted with that same hash: https://ci-artifacts.kibana.dev/storybooks/main/5ad3ef7b0a76968a31b0824bd08f9132c374c841/shared_ux/index.html So this PR alters the URL so you can consistently point to the latest Storybook build: https://ci-artifacts.kibana.dev/storybooks/main/shared_ux/index.html |
||
|---|---|---|
| .. | ||
| hooks | ||
| pipeline-resource-definitions | ||
| pipeline-utils | ||
| pipelines | ||
| scripts | ||
| .mocharc.json | ||
| .npmrc | ||
| disabled_jest_configs.json | ||
| ftr_base_serverless_configs.yml | ||
| ftr_configs_manifests.json | ||
| ftr_oblt_serverless_configs.yml | ||
| ftr_oblt_stateful_configs.yml | ||
| ftr_platform_stateful_configs.yml | ||
| ftr_search_serverless_configs.yml | ||
| ftr_search_stateful_configs.yml | ||
| ftr_security_serverless_configs.yml | ||
| ftr_security_stateful_configs.yml | ||
| package-lock.json | ||
| package.json | ||
| pull_requests.json | ||
| README.md | ||
| tsconfig.json | ||
| tsconfig.test.json | ||
Kibana / Buildkite
Directory Structure
hooks- special directory used by Buildkite agents for hookspipeline-utils- Shared TypeScript utils for use in pipeline scriptspipelines- contains pipeline definitionsscripts/common- scripts that getsourced by other scripts to set environment variables or import shared functionsscripts/lifecycle- general scripts for tasks that run before or after individual steps or the entire buildscripts/steps- scripts that define something that will run for a step defined in a pipelinescripts/*- all other scripts are building blocks that make up the tasks in pipelines. They may be run by other scripts, but should not besourced