Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Browse files
Browse the repository at this point in the history
# Backport This will backport the following commits from `main` to `8.11`: - [[ci/pull_requests] Disable kibana-kme-test (#169238)](#169238) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Jon","email":"[email protected]"},"sourceCommit":{"committedDate":"2023-10-23T18:47:15Z","message":"[ci/pull_requests] Disable kibana-kme-test (#169238)\n\nIntroduced in https://github.com/elastic/kibana/pull/157334\r\n\r\nThis pipeline was/(is?) used for testing the new buildkite system. We're\r\nrunning into an issue where `trigger_comment_regex` matches on both the\r\nlegacy and new systems, triggering builds in both. GitHub checks can end\r\nup conflicting making it difficult to find the correct build link.\r\n\r\nThis disables the pr integration for kibana-kme-test. If we're done with\r\nthe testing pipeline we can remove it, if not we can change the trigger\r\nword. I'm not sure what the current status is, ping @elastic/ci-systems\r\n.","sha":"0ec93317c1d099e29dbfac2327df449cc1da0a40","branchLabelMapping":{"^v8.12.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Operations","release_note:skip","backport:prev-minor","v8.12.0"],"number":169238,"url":"https://github.com/elastic/kibana/pull/169238","mergeCommit":{"message":"[ci/pull_requests] Disable kibana-kme-test (#169238)\n\nIntroduced in https://github.com/elastic/kibana/pull/157334\r\n\r\nThis pipeline was/(is?) used for testing the new buildkite system. We're\r\nrunning into an issue where `trigger_comment_regex` matches on both the\r\nlegacy and new systems, triggering builds in both. GitHub checks can end\r\nup conflicting making it difficult to find the correct build link.\r\n\r\nThis disables the pr integration for kibana-kme-test. If we're done with\r\nthe testing pipeline we can remove it, if not we can change the trigger\r\nword. I'm not sure what the current status is, ping @elastic/ci-systems\r\n.","sha":"0ec93317c1d099e29dbfac2327df449cc1da0a40"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.12.0","labelRegex":"^v8.12.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/169238","number":169238,"mergeCommit":{"message":"[ci/pull_requests] Disable kibana-kme-test (#169238)\n\nIntroduced in https://github.com/elastic/kibana/pull/157334\r\n\r\nThis pipeline was/(is?) used for testing the new buildkite system. We're\r\nrunning into an issue where `trigger_comment_regex` matches on both the\r\nlegacy and new systems, triggering builds in both. GitHub checks can end\r\nup conflicting making it difficult to find the correct build link.\r\n\r\nThis disables the pr integration for kibana-kme-test. If we're done with\r\nthe testing pipeline we can remove it, if not we can change the trigger\r\nword. I'm not sure what the current status is, ping @elastic/ci-systems\r\n.","sha":"0ec93317c1d099e29dbfac2327df449cc1da0a40"}}]}] BACKPORT--> Co-authored-by: Jon <[email protected]>
- Loading branch information