mirror of
https://github.com/elastic/kibana.git
synced 2025-06-27 18:51:07 -04:00
284e404945
# Backport This will backport the following commits from `main` to `9.0`: - [Update console definitions branches (#221888)](https://github.com/elastic/kibana/pull/221888) <!--- Backport version: 10.0.0 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Sonia Sanz Vivas","email":"sonia.sanzvivas@elastic.co"},"sourceCommit":{"committedDate":"2025-05-29T16:35:17Z","message":"Update console definitions branches (#221888)\n\n## Summary\n\nWith https://github.com/elastic/kibana/pull/207036 we introduced some\nchanges in the script so that it generates two PRs: one for the `main`\nbranch and one for `8.x` in order to keep previous versions with their\ncorresponding console definitions.\n\nThis PR updates the branches so the script generates PRs for `main`,\n`9.0`, `8.19` and `8.18`","sha":"abf2c2c789dd3ad4f727d59ec292b32d0e9e84e8","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Console","Team:Kibana Management","release_note:skip","backport:version","v9.1.0","v8.19.0","v9.0.2","v8.18.3"],"title":"Update console definitions branches","number":221888,"url":"https://github.com/elastic/kibana/pull/221888","mergeCommit":{"message":"Update console definitions branches (#221888)\n\n## Summary\n\nWith https://github.com/elastic/kibana/pull/207036 we introduced some\nchanges in the script so that it generates two PRs: one for the `main`\nbranch and one for `8.x` in order to keep previous versions with their\ncorresponding console definitions.\n\nThis PR updates the branches so the script generates PRs for `main`,\n`9.0`, `8.19` and `8.18`","sha":"abf2c2c789dd3ad4f727d59ec292b32d0e9e84e8"}},"sourceBranch":"main","suggestedTargetBranches":["8.19","9.0","8.18"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/221888","number":221888,"mergeCommit":{"message":"Update console definitions branches (#221888)\n\n## Summary\n\nWith https://github.com/elastic/kibana/pull/207036 we introduced some\nchanges in the script so that it generates two PRs: one for the `main`\nbranch and one for `8.x` in order to keep previous versions with their\ncorresponding console definitions.\n\nThis PR updates the branches so the script generates PRs for `main`,\n`9.0`, `8.19` and `8.18`","sha":"abf2c2c789dd3ad4f727d59ec292b32d0e9e84e8"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.2","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|---|---|---|
| .. | ||
| _templates | ||
| scripts | ||
| security-solution-ess | ||
| security-solution-quality-gate | ||
| kibana-api-docs.yml | ||
| kibana-apis-capacity-testing-daily.yml | ||
| kibana-artifacts-container-image.yml | ||
| kibana-artifacts-snapshot.yml | ||
| kibana-artifacts-staging.yml | ||
| kibana-artifacts-trigger.yml | ||
| kibana-chrome-forward-testing.yml | ||
| kibana-codeql.yml | ||
| kibana-console-definitions-sync.yml | ||
| kibana-coverage-daily.yml | ||
| kibana-deploy-cloud.yml | ||
| kibana-deploy-project.yml | ||
| kibana-es-forward-testing-9-dot-0.yml | ||
| kibana-es-forward-testing.yml | ||
| kibana-es-serverless-snapshots.yml | ||
| kibana-es-snapshots.yml | ||
| kibana-esql-grammar-sync.yml | ||
| kibana-fips-daily.yml | ||
| kibana-flaky.yml | ||
| kibana-fleet-packages-daily.yml | ||
| kibana-gen-ai-daily.yml | ||
| kibana-migration-staging.yml | ||
| kibana-on-merge-unsupported-ftrs.yml | ||
| kibana-on-merge.yml | ||
| kibana-package-registry.yml | ||
| kibana-performance-daily.yml | ||
| kibana-performance-data-set-extraction-daily.yml | ||
| kibana-pointer-compression.yml | ||
| kibana-pr.yml | ||
| kibana-purge-cloud-deployments.yml | ||
| kibana-serverless-emergency-release.yml | ||
| kibana-serverless-quality-gates-emergency.yml | ||
| kibana-serverless-quality-gates.yml | ||
| kibana-serverless-release-testing.yml | ||
| kibana-serverless-release.yml | ||
| kibana-vm-images.yml | ||
| locations.yml | ||
| README.md | ||
| scalability_testing-daily.yml | ||
| trigger-version-dependent-jobs.yml | ||
Buildkite pipeline resource definitions
Overview
The pipeline resources are "RRE" (real resource entities) that are used to create/maintain buildkite pipelines.
The resources described in these files are parsed and loaded to Backstage (https://backstage.elastic.dev). From there, Terrazzo is generating and updating the buildkite pipelines.
These pipelines are referenced indirectly through the root's catalog-info.yaml file in order to reduce bloat in the main resources file.
There's a location file that collects files defined in this folder (locations.yml), this file needs to be updated in order to keep track of local files.
Available parameters and further help can be found here: https://docs.elastic.dev/ci/getting-started-with-buildkite-at-elastic
Creating a new pipeline resource definition
The easiest way to create a new pipeline is either by copying and editing a similar pipeline, or by copying a blank template (see _new_pipeline.yml) and editing that.
You can validate your pipeline's structural integrity, and it's conformity to baseline rules by running the following command:
.buildkite/pipeline-resource-definitions/scripts/validate-pipeline-definition.sh <path_to_your_pipeline_file>
Once you've added the file, you should update the locations.yml file to include the new pipeline, or run the following command to update it:
.buildkite/pipeline-resource-definitions/scripts/fix-location-collection.ts
Add your pipeline implementation, commit & push & merge. The pipeline resource will appear in Backstage within minutes, then the pipeline will be added to Buildkite within ~10 minutes.