github-mirrors/kibana
1
0
Fork 0
mirror of https://github.com/elastic/kibana.git synced 2025-04-24 01:38:56 -04:00
Code Issues Projects Releases Packages Wiki Activity

[8.11] [ci/pull_requests] Disable kibana-kme-test (#169238) (#169568)

Browse source 
# Backport

This will backport the following commits from `main` to `8.11`:
- [[ci/pull_requests] Disable kibana-kme-test
(#169238)](https://github.com/elastic/kibana/pull/169238)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT
[{"author":{"name":"Jon","email":"jon@elastic.co"},"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 <jon@elastic.co>
This commit is contained in:
Kibana Machine 2023-10-23 15:11:10 -04:00 • committed by GitHub
parent 09f6923e7c
commit 412f0da01b
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

2
.buildkite/pull_requests.json
View file

@ -55,7 +55,7 @@
"repoName": "kibana",
"pipelineSlug": "kibana-kme-test",
"enabled": true,
"enabled": false,
"allow_org_users": true,
"allowed_repo_permissions": ["admin", "write"],
"allowed_list": ["barlowm", "renovate[bot]"],