Skip to content

[CI] Fix Renovate helper bot trigger and out of sync labels#231031

Merged
Ikuni17 merged 2 commits intoelastic:mainfrom
Ikuni17:fix/renovate-helper-bot-trigger
Aug 8, 2025
Merged

[CI] Fix Renovate helper bot trigger and out of sync labels#231031
Ikuni17 merged 2 commits intoelastic:mainfrom
Ikuni17:fix/renovate-helper-bot-trigger

Conversation

@Ikuni17
Copy link
Copy Markdown
Contributor

@Ikuni17 Ikuni17 commented Aug 7, 2025

Summary

Note: I will backport this after backporting the original PR #228664. I was waiting to see the stability of the original PR.

Fixes two issues:

  • The pipeline is not triggering for Renovate PRs, unless explicitly commenting to run
  • Since we're passing along GITHUB_PR_* env variables to the PR pipeline. Labels added in the helper pipeline to the PR itself were not in sync with the PR run. Example this run should have ci:cloud-deploy label.

@Ikuni17 Ikuni17 self-assigned this Aug 7, 2025
@Ikuni17 Ikuni17 requested a review from a team as a code owner August 7, 2025 19:38
@Ikuni17 Ikuni17 added Team:Operations Kibana-Operations Team release_note:skip Skip the PR/issue when compiling release notes backport:skip This PR does not require backporting labels Aug 7, 2025
@elasticmachine
Copy link
Copy Markdown
Contributor

Pinging @elastic/kibana-operations (Team:Operations)

@elasticmachine
Copy link
Copy Markdown
Contributor

💚 Build Succeeded

Metrics [docs]

✅ unchanged

cc @Ikuni17

@Ikuni17 Ikuni17 requested a review from Copilot August 7, 2025 22:51
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR fixes two issues with the Renovate helper bot and CI pipeline integration. The main goal is to ensure the Renovate helper pipeline triggers correctly and maintains label synchronization between the helper and main PR pipelines.

  • Added the Renovate bot to the allowed list for triggering PR builds
  • Implemented label synchronization by updating the GITHUB_PR_LABELS environment variable when the helper pipeline adds labels

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File Description
.buildkite/pull_requests.json Added elastic-renovate-prod[bot] to the allowed list for triggering builds
.buildkite/scripts/steps/renovate/renovate_helper.sh Added logic to sync the GITHUB_PR_LABELS environment variable when adding the ci:cloud-deploy label
Comments suppressed due to low confidence (1)

@Ikuni17 Ikuni17 merged commit f61e1a2 into elastic:main Aug 8, 2025
20 checks passed
@Ikuni17 Ikuni17 added backport:prev-major and removed backport:skip This PR does not require backporting labels Aug 8, 2025
@kibanamachine
Copy link
Copy Markdown
Contributor

Starting backport for target branches: 8.17, 8.18, 8.19, 9.0, 9.1

https://github.com/elastic/kibana/actions/runs/16842567522

@kibanamachine
Copy link
Copy Markdown
Contributor

Starting backport for target branches: 8.17, 8.18, 8.19, 9.0, 9.1

https://github.com/elastic/kibana/actions/runs/16842567524

@kibanamachine
Copy link
Copy Markdown
Contributor

Starting backport for target branches: 8.17, 8.18, 8.19, 9.0, 9.1

https://github.com/elastic/kibana/actions/runs/16842567531

kibanamachine pushed a commit to kibanamachine/kibana that referenced this pull request Aug 8, 2025
…231031)

## Summary

Note: I will backport this after backporting the original PR elastic#228664. I
was waiting to see the stability of the original PR.

Fixes two issues:
- The [pipeline](https://buildkite.com/elastic/kibana-renovate-helper)
is not triggering for Renovate PRs, unless explicitly
[commenting](elastic#230882 (comment))
to run
- Since we're passing along `GITHUB_PR_*` env variables to the PR
pipeline. Labels added in the helper pipeline to the PR itself were not
in sync with the PR run. Example [this
run](https://buildkite.com/elastic/kibana-pull-request/builds/327690#019885d3-196a-4950-896c-3bf7de6f735f)
should have `ci:cloud-deploy` label.

(cherry picked from commit f61e1a2)
@kibanamachine
Copy link
Copy Markdown
Contributor

💔 Some backports could not be created

Status Branch Result
8.17 Backport failed because of merge conflicts
8.18 Backport failed because of merge conflicts
8.19 Backport failed because of merge conflicts
9.0 Backport failed because of merge conflicts
9.1

Note: Successful backport PRs will be merged automatically after passing CI.

Manual backport

To create the backport manually run:

node scripts/backport --pr 231031

Questions ?

Please refer to the Backport tool documentation

kibanamachine pushed a commit to kibanamachine/kibana that referenced this pull request Aug 8, 2025
…231031)

## Summary

Note: I will backport this after backporting the original PR elastic#228664. I
was waiting to see the stability of the original PR.

Fixes two issues:
- The [pipeline](https://buildkite.com/elastic/kibana-renovate-helper)
is not triggering for Renovate PRs, unless explicitly
[commenting](elastic#230882 (comment))
to run
- Since we're passing along `GITHUB_PR_*` env variables to the PR
pipeline. Labels added in the helper pipeline to the PR itself were not
in sync with the PR run. Example [this
run](https://buildkite.com/elastic/kibana-pull-request/builds/327690#019885d3-196a-4950-896c-3bf7de6f735f)
should have `ci:cloud-deploy` label.

(cherry picked from commit f61e1a2)
@kibanamachine
Copy link
Copy Markdown
Contributor

💔 Some backports could not be created

Status Branch Result
8.17 Backport failed because of merge conflicts
8.18 Backport failed because of merge conflicts
8.19 Backport failed because of merge conflicts
9.0 Backport failed because of merge conflicts
9.1

Note: Successful backport PRs will be merged automatically after passing CI.

Manual backport

To create the backport manually run:

node scripts/backport --pr 231031

Questions ?

Please refer to the Backport tool documentation

kibanamachine pushed a commit to kibanamachine/kibana that referenced this pull request Aug 8, 2025
…231031)

## Summary

Note: I will backport this after backporting the original PR elastic#228664. I
was waiting to see the stability of the original PR.

Fixes two issues:
- The [pipeline](https://buildkite.com/elastic/kibana-renovate-helper)
is not triggering for Renovate PRs, unless explicitly
[commenting](elastic#230882 (comment))
to run
- Since we're passing along `GITHUB_PR_*` env variables to the PR
pipeline. Labels added in the helper pipeline to the PR itself were not
in sync with the PR run. Example [this
run](https://buildkite.com/elastic/kibana-pull-request/builds/327690#019885d3-196a-4950-896c-3bf7de6f735f)
should have `ci:cloud-deploy` label.

(cherry picked from commit f61e1a2)
@kibanamachine
Copy link
Copy Markdown
Contributor

💔 Some backports could not be created

Status Branch Result
8.17 Backport failed because of merge conflicts
8.18 Backport failed because of merge conflicts
8.19 Backport failed because of merge conflicts
9.0 Backport failed because of merge conflicts
9.1

Note: Successful backport PRs will be merged automatically after passing CI.

Manual backport

To create the backport manually run:

node scripts/backport --pr 231031

Questions ?

Please refer to the Backport tool documentation

Ikuni17 added a commit to Ikuni17/kibana that referenced this pull request Aug 8, 2025
…231031)

## Summary

Note: I will backport this after backporting the original PR elastic#228664. I
was waiting to see the stability of the original PR.

Fixes two issues:
- The [pipeline](https://buildkite.com/elastic/kibana-renovate-helper)
is not triggering for Renovate PRs, unless explicitly
[commenting](elastic#230882 (comment))
to run
- Since we're passing along `GITHUB_PR_*` env variables to the PR
pipeline. Labels added in the helper pipeline to the PR itself were not
in sync with the PR run. Example [this
run](https://buildkite.com/elastic/kibana-pull-request/builds/327690#019885d3-196a-4950-896c-3bf7de6f735f)
should have `ci:cloud-deploy` label.

(cherry picked from commit f61e1a2)

# Conflicts:
#	.buildkite/pull_requests.json
Ikuni17 added a commit to Ikuni17/kibana that referenced this pull request Aug 8, 2025
…231031)

## Summary

Note: I will backport this after backporting the original PR elastic#228664. I
was waiting to see the stability of the original PR.

Fixes two issues:
- The [pipeline](https://buildkite.com/elastic/kibana-renovate-helper)
is not triggering for Renovate PRs, unless explicitly
[commenting](elastic#230882 (comment))
to run
- Since we're passing along `GITHUB_PR_*` env variables to the PR
pipeline. Labels added in the helper pipeline to the PR itself were not
in sync with the PR run. Example [this
run](https://buildkite.com/elastic/kibana-pull-request/builds/327690#019885d3-196a-4950-896c-3bf7de6f735f)
should have `ci:cloud-deploy` label.

(cherry picked from commit f61e1a2)

# Conflicts:
#	.buildkite/pull_requests.json
Ikuni17 added a commit to Ikuni17/kibana that referenced this pull request Aug 8, 2025
…231031)

## Summary

Note: I will backport this after backporting the original PR elastic#228664. I
was waiting to see the stability of the original PR.

Fixes two issues:
- The [pipeline](https://buildkite.com/elastic/kibana-renovate-helper)
is not triggering for Renovate PRs, unless explicitly
[commenting](elastic#230882 (comment))
to run
- Since we're passing along `GITHUB_PR_*` env variables to the PR
pipeline. Labels added in the helper pipeline to the PR itself were not
in sync with the PR run. Example [this
run](https://buildkite.com/elastic/kibana-pull-request/builds/327690#019885d3-196a-4950-896c-3bf7de6f735f)
should have `ci:cloud-deploy` label.

(cherry picked from commit f61e1a2)

# Conflicts:
#	.buildkite/pull_requests.json
@Ikuni17
Copy link
Copy Markdown
Contributor Author

Ikuni17 commented Aug 8, 2025

💚 All backports created successfully

Status Branch Result
9.0
8.19
8.18
8.17

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation

@Ikuni17 Ikuni17 deleted the fix/renovate-helper-bot-trigger branch August 8, 2025 23:52
Ikuni17 added a commit to Ikuni17/kibana that referenced this pull request Aug 8, 2025
…231031)

## Summary

Note: I will backport this after backporting the original PR elastic#228664. I
was waiting to see the stability of the original PR.

Fixes two issues:
- The [pipeline](https://buildkite.com/elastic/kibana-renovate-helper)
is not triggering for Renovate PRs, unless explicitly
[commenting](elastic#230882 (comment))
to run
- Since we're passing along `GITHUB_PR_*` env variables to the PR
pipeline. Labels added in the helper pipeline to the PR itself were not
in sync with the PR run. Example [this
run](https://buildkite.com/elastic/kibana-pull-request/builds/327690#019885d3-196a-4950-896c-3bf7de6f735f)
should have `ci:cloud-deploy` label.

(cherry picked from commit f61e1a2)

# Conflicts:
#	.buildkite/pull_requests.json
Ikuni17 added a commit that referenced this pull request Aug 8, 2025
…31031) (#231216)

# Backport

This will backport the following commits from `main` to `9.1`:
- [[CI] Fix Renovate helper bot trigger and out of sync labels
(#231031)](#231031)

<!--- Backport version: 9.6.6 -->

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

<!--BACKPORT [{"author":{"name":"Brad
White","email":"Ikuni17@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-08-08T17:00:42Z","message":"[CI]
Fix Renovate helper bot trigger and out of sync labels (#231031)\n\n##
Summary\n\nNote: I will backport this after backporting the original PR
#228664. I\nwas waiting to see the stability of the original
PR.\n\nFixes two issues:\n- The
[pipeline](https://buildkite.com/elastic/kibana-renovate-helper)\nis not
triggering for Renovate PRs, unless
explicitly\n[commenting](https://github.com/elastic/kibana/pull/230882#issuecomment-3165286181)\nto
run\n- Since we're passing along `GITHUB_PR_*` env variables to the
PR\npipeline. Labels added in the helper pipeline to the PR itself were
not\nin sync with the PR run. Example
[this\nrun](https://buildkite.com/elastic/kibana-pull-request/builds/327690#019885d3-196a-4950-896c-3bf7de6f735f)\nshould
have `ci:cloud-deploy`
label.","sha":"f61e1a2bb618c2f0f7586acb61721c76b0102674","branchLabelMapping":{"^v9.2.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Operations","release_note:skip","backport:prev-major","backport:current-major","v9.2.0"],"title":"[CI]
Fix Renovate helper bot trigger and out of sync
labels","number":231031,"url":"https://github.com/elastic/kibana/pull/231031","mergeCommit":{"message":"[CI]
Fix Renovate helper bot trigger and out of sync labels (#231031)\n\n##
Summary\n\nNote: I will backport this after backporting the original PR
#228664. I\nwas waiting to see the stability of the original
PR.\n\nFixes two issues:\n- The
[pipeline](https://buildkite.com/elastic/kibana-renovate-helper)\nis not
triggering for Renovate PRs, unless
explicitly\n[commenting](https://github.com/elastic/kibana/pull/230882#issuecomment-3165286181)\nto
run\n- Since we're passing along `GITHUB_PR_*` env variables to the
PR\npipeline. Labels added in the helper pipeline to the PR itself were
not\nin sync with the PR run. Example
[this\nrun](https://buildkite.com/elastic/kibana-pull-request/builds/327690#019885d3-196a-4950-896c-3bf7de6f735f)\nshould
have `ci:cloud-deploy`
label.","sha":"f61e1a2bb618c2f0f7586acb61721c76b0102674"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.2.0","branchLabelMappingKey":"^v9.2.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/231031","number":231031,"mergeCommit":{"message":"[CI]
Fix Renovate helper bot trigger and out of sync labels (#231031)\n\n##
Summary\n\nNote: I will backport this after backporting the original PR
#228664. I\nwas waiting to see the stability of the original
PR.\n\nFixes two issues:\n- The
[pipeline](https://buildkite.com/elastic/kibana-renovate-helper)\nis not
triggering for Renovate PRs, unless
explicitly\n[commenting](https://github.com/elastic/kibana/pull/230882#issuecomment-3165286181)\nto
run\n- Since we're passing along `GITHUB_PR_*` env variables to the
PR\npipeline. Labels added in the helper pipeline to the PR itself were
not\nin sync with the PR run. Example
[this\nrun](https://buildkite.com/elastic/kibana-pull-request/builds/327690#019885d3-196a-4950-896c-3bf7de6f735f)\nshould
have `ci:cloud-deploy`
label.","sha":"f61e1a2bb618c2f0f7586acb61721c76b0102674"}}]}]
BACKPORT-->

Co-authored-by: Brad White <Ikuni17@users.noreply.github.com>
Ikuni17 added a commit that referenced this pull request Aug 8, 2025
…31031) (#231218)

# Backport

This will backport the following commits from `main` to `9.0`:
- [[CI] Fix Renovate helper bot trigger and out of sync labels
(#231031)](#231031)

<!--- Backport version: 10.0.1 -->

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

<!--BACKPORT [{"author":{"name":"Brad
White","email":"Ikuni17@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-08-08T17:00:42Z","message":"[CI]
Fix Renovate helper bot trigger and out of sync labels (#231031)\n\n##
Summary\n\nNote: I will backport this after backporting the original PR
#228664. I\nwas waiting to see the stability of the original
PR.\n\nFixes two issues:\n- The
[pipeline](https://buildkite.com/elastic/kibana-renovate-helper)\nis not
triggering for Renovate PRs, unless
explicitly\n[commenting](https://github.com/elastic/kibana/pull/230882#issuecomment-3165286181)\nto
run\n- Since we're passing along `GITHUB_PR_*` env variables to the
PR\npipeline. Labels added in the helper pipeline to the PR itself were
not\nin sync with the PR run. Example
[this\nrun](https://buildkite.com/elastic/kibana-pull-request/builds/327690#019885d3-196a-4950-896c-3bf7de6f735f)\nshould
have `ci:cloud-deploy`
label.","sha":"f61e1a2bb618c2f0f7586acb61721c76b0102674","branchLabelMapping":{"^v9.2.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Operations","release_note:skip","backport:prev-major","backport:current-major","v9.2.0"],"title":"[CI]
Fix Renovate helper bot trigger and out of sync
labels","number":231031,"url":"https://github.com/elastic/kibana/pull/231031","mergeCommit":{"message":"[CI]
Fix Renovate helper bot trigger and out of sync labels (#231031)\n\n##
Summary\n\nNote: I will backport this after backporting the original PR
#228664. I\nwas waiting to see the stability of the original
PR.\n\nFixes two issues:\n- The
[pipeline](https://buildkite.com/elastic/kibana-renovate-helper)\nis not
triggering for Renovate PRs, unless
explicitly\n[commenting](https://github.com/elastic/kibana/pull/230882#issuecomment-3165286181)\nto
run\n- Since we're passing along `GITHUB_PR_*` env variables to the
PR\npipeline. Labels added in the helper pipeline to the PR itself were
not\nin sync with the PR run. Example
[this\nrun](https://buildkite.com/elastic/kibana-pull-request/builds/327690#019885d3-196a-4950-896c-3bf7de6f735f)\nshould
have `ci:cloud-deploy`
label.","sha":"f61e1a2bb618c2f0f7586acb61721c76b0102674"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.2.0","branchLabelMappingKey":"^v9.2.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/231031","number":231031,"mergeCommit":{"message":"[CI]
Fix Renovate helper bot trigger and out of sync labels (#231031)\n\n##
Summary\n\nNote: I will backport this after backporting the original PR
#228664. I\nwas waiting to see the stability of the original
PR.\n\nFixes two issues:\n- The
[pipeline](https://buildkite.com/elastic/kibana-renovate-helper)\nis not
triggering for Renovate PRs, unless
explicitly\n[commenting](https://github.com/elastic/kibana/pull/230882#issuecomment-3165286181)\nto
run\n- Since we're passing along `GITHUB_PR_*` env variables to the
PR\npipeline. Labels added in the helper pipeline to the PR itself were
not\nin sync with the PR run. Example
[this\nrun](https://buildkite.com/elastic/kibana-pull-request/builds/327690#019885d3-196a-4950-896c-3bf7de6f735f)\nshould
have `ci:cloud-deploy`
label.","sha":"f61e1a2bb618c2f0f7586acb61721c76b0102674"}},{"url":"https://github.com/elastic/kibana/pull/231216","number":231216,"branch":"9.1","state":"OPEN"}]}]
BACKPORT-->
Ikuni17 added a commit that referenced this pull request Aug 8, 2025
…231031) (#231219)

# Backport

This will backport the following commits from `main` to `8.19`:
- [[CI] Fix Renovate helper bot trigger and out of sync labels
(#231031)](#231031)

<!--- Backport version: 10.0.1 -->

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

<!--BACKPORT [{"author":{"name":"Brad
White","email":"Ikuni17@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-08-08T17:00:42Z","message":"[CI]
Fix Renovate helper bot trigger and out of sync labels (#231031)\n\n##
Summary\n\nNote: I will backport this after backporting the original PR
#228664. I\nwas waiting to see the stability of the original
PR.\n\nFixes two issues:\n- The
[pipeline](https://buildkite.com/elastic/kibana-renovate-helper)\nis not
triggering for Renovate PRs, unless
explicitly\n[commenting](https://github.com/elastic/kibana/pull/230882#issuecomment-3165286181)\nto
run\n- Since we're passing along `GITHUB_PR_*` env variables to the
PR\npipeline. Labels added in the helper pipeline to the PR itself were
not\nin sync with the PR run. Example
[this\nrun](https://buildkite.com/elastic/kibana-pull-request/builds/327690#019885d3-196a-4950-896c-3bf7de6f735f)\nshould
have `ci:cloud-deploy`
label.","sha":"f61e1a2bb618c2f0f7586acb61721c76b0102674","branchLabelMapping":{"^v9.2.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Operations","release_note:skip","backport:prev-major","backport:current-major","v9.2.0"],"title":"[CI]
Fix Renovate helper bot trigger and out of sync
labels","number":231031,"url":"https://github.com/elastic/kibana/pull/231031","mergeCommit":{"message":"[CI]
Fix Renovate helper bot trigger and out of sync labels (#231031)\n\n##
Summary\n\nNote: I will backport this after backporting the original PR
#228664. I\nwas waiting to see the stability of the original
PR.\n\nFixes two issues:\n- The
[pipeline](https://buildkite.com/elastic/kibana-renovate-helper)\nis not
triggering for Renovate PRs, unless
explicitly\n[commenting](https://github.com/elastic/kibana/pull/230882#issuecomment-3165286181)\nto
run\n- Since we're passing along `GITHUB_PR_*` env variables to the
PR\npipeline. Labels added in the helper pipeline to the PR itself were
not\nin sync with the PR run. Example
[this\nrun](https://buildkite.com/elastic/kibana-pull-request/builds/327690#019885d3-196a-4950-896c-3bf7de6f735f)\nshould
have `ci:cloud-deploy`
label.","sha":"f61e1a2bb618c2f0f7586acb61721c76b0102674"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.2.0","branchLabelMappingKey":"^v9.2.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/231031","number":231031,"mergeCommit":{"message":"[CI]
Fix Renovate helper bot trigger and out of sync labels (#231031)\n\n##
Summary\n\nNote: I will backport this after backporting the original PR
#228664. I\nwas waiting to see the stability of the original
PR.\n\nFixes two issues:\n- The
[pipeline](https://buildkite.com/elastic/kibana-renovate-helper)\nis not
triggering for Renovate PRs, unless
explicitly\n[commenting](https://github.com/elastic/kibana/pull/230882#issuecomment-3165286181)\nto
run\n- Since we're passing along `GITHUB_PR_*` env variables to the
PR\npipeline. Labels added in the helper pipeline to the PR itself were
not\nin sync with the PR run. Example
[this\nrun](https://buildkite.com/elastic/kibana-pull-request/builds/327690#019885d3-196a-4950-896c-3bf7de6f735f)\nshould
have `ci:cloud-deploy`
label.","sha":"f61e1a2bb618c2f0f7586acb61721c76b0102674"}},{"url":"https://github.com/elastic/kibana/pull/231216","number":231216,"branch":"9.1","state":"OPEN"}]}]
BACKPORT-->
Ikuni17 added a commit that referenced this pull request Aug 8, 2025
…231031) (#231220)

# Backport

This will backport the following commits from `main` to `8.18`:
- [[CI] Fix Renovate helper bot trigger and out of sync labels
(#231031)](#231031)

<!--- Backport version: 10.0.1 -->

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

<!--BACKPORT [{"author":{"name":"Brad
White","email":"Ikuni17@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-08-08T17:00:42Z","message":"[CI]
Fix Renovate helper bot trigger and out of sync labels (#231031)\n\n##
Summary\n\nNote: I will backport this after backporting the original PR
#228664. I\nwas waiting to see the stability of the original
PR.\n\nFixes two issues:\n- The
[pipeline](https://buildkite.com/elastic/kibana-renovate-helper)\nis not
triggering for Renovate PRs, unless
explicitly\n[commenting](https://github.com/elastic/kibana/pull/230882#issuecomment-3165286181)\nto
run\n- Since we're passing along `GITHUB_PR_*` env variables to the
PR\npipeline. Labels added in the helper pipeline to the PR itself were
not\nin sync with the PR run. Example
[this\nrun](https://buildkite.com/elastic/kibana-pull-request/builds/327690#019885d3-196a-4950-896c-3bf7de6f735f)\nshould
have `ci:cloud-deploy`
label.","sha":"f61e1a2bb618c2f0f7586acb61721c76b0102674","branchLabelMapping":{"^v9.2.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Operations","release_note:skip","backport:prev-major","backport:current-major","v9.2.0"],"title":"[CI]
Fix Renovate helper bot trigger and out of sync
labels","number":231031,"url":"https://github.com/elastic/kibana/pull/231031","mergeCommit":{"message":"[CI]
Fix Renovate helper bot trigger and out of sync labels (#231031)\n\n##
Summary\n\nNote: I will backport this after backporting the original PR
#228664. I\nwas waiting to see the stability of the original
PR.\n\nFixes two issues:\n- The
[pipeline](https://buildkite.com/elastic/kibana-renovate-helper)\nis not
triggering for Renovate PRs, unless
explicitly\n[commenting](https://github.com/elastic/kibana/pull/230882#issuecomment-3165286181)\nto
run\n- Since we're passing along `GITHUB_PR_*` env variables to the
PR\npipeline. Labels added in the helper pipeline to the PR itself were
not\nin sync with the PR run. Example
[this\nrun](https://buildkite.com/elastic/kibana-pull-request/builds/327690#019885d3-196a-4950-896c-3bf7de6f735f)\nshould
have `ci:cloud-deploy`
label.","sha":"f61e1a2bb618c2f0f7586acb61721c76b0102674"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.2.0","branchLabelMappingKey":"^v9.2.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/231031","number":231031,"mergeCommit":{"message":"[CI]
Fix Renovate helper bot trigger and out of sync labels (#231031)\n\n##
Summary\n\nNote: I will backport this after backporting the original PR
#228664. I\nwas waiting to see the stability of the original
PR.\n\nFixes two issues:\n- The
[pipeline](https://buildkite.com/elastic/kibana-renovate-helper)\nis not
triggering for Renovate PRs, unless
explicitly\n[commenting](https://github.com/elastic/kibana/pull/230882#issuecomment-3165286181)\nto
run\n- Since we're passing along `GITHUB_PR_*` env variables to the
PR\npipeline. Labels added in the helper pipeline to the PR itself were
not\nin sync with the PR run. Example
[this\nrun](https://buildkite.com/elastic/kibana-pull-request/builds/327690#019885d3-196a-4950-896c-3bf7de6f735f)\nshould
have `ci:cloud-deploy`
label.","sha":"f61e1a2bb618c2f0f7586acb61721c76b0102674"}},{"url":"https://github.com/elastic/kibana/pull/231216","number":231216,"branch":"9.1","state":"OPEN"}]}]
BACKPORT-->
Ikuni17 added a commit that referenced this pull request Aug 8, 2025
…231031) (#231221)

# Backport

This will backport the following commits from `main` to `8.17`:
- [[CI] Fix Renovate helper bot trigger and out of sync labels
(#231031)](#231031)

<!--- Backport version: 10.0.1 -->

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

<!--BACKPORT [{"author":{"name":"Brad
White","email":"Ikuni17@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-08-08T17:00:42Z","message":"[CI]
Fix Renovate helper bot trigger and out of sync labels (#231031)\n\n##
Summary\n\nNote: I will backport this after backporting the original PR
#228664. I\nwas waiting to see the stability of the original
PR.\n\nFixes two issues:\n- The
[pipeline](https://buildkite.com/elastic/kibana-renovate-helper)\nis not
triggering for Renovate PRs, unless
explicitly\n[commenting](https://github.com/elastic/kibana/pull/230882#issuecomment-3165286181)\nto
run\n- Since we're passing along `GITHUB_PR_*` env variables to the
PR\npipeline. Labels added in the helper pipeline to the PR itself were
not\nin sync with the PR run. Example
[this\nrun](https://buildkite.com/elastic/kibana-pull-request/builds/327690#019885d3-196a-4950-896c-3bf7de6f735f)\nshould
have `ci:cloud-deploy`
label.","sha":"f61e1a2bb618c2f0f7586acb61721c76b0102674","branchLabelMapping":{"^v9.2.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Operations","release_note:skip","backport:prev-major","backport:current-major","v9.2.0"],"title":"[CI]
Fix Renovate helper bot trigger and out of sync
labels","number":231031,"url":"https://github.com/elastic/kibana/pull/231031","mergeCommit":{"message":"[CI]
Fix Renovate helper bot trigger and out of sync labels (#231031)\n\n##
Summary\n\nNote: I will backport this after backporting the original PR
#228664. I\nwas waiting to see the stability of the original
PR.\n\nFixes two issues:\n- The
[pipeline](https://buildkite.com/elastic/kibana-renovate-helper)\nis not
triggering for Renovate PRs, unless
explicitly\n[commenting](https://github.com/elastic/kibana/pull/230882#issuecomment-3165286181)\nto
run\n- Since we're passing along `GITHUB_PR_*` env variables to the
PR\npipeline. Labels added in the helper pipeline to the PR itself were
not\nin sync with the PR run. Example
[this\nrun](https://buildkite.com/elastic/kibana-pull-request/builds/327690#019885d3-196a-4950-896c-3bf7de6f735f)\nshould
have `ci:cloud-deploy`
label.","sha":"f61e1a2bb618c2f0f7586acb61721c76b0102674"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.2.0","branchLabelMappingKey":"^v9.2.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/231031","number":231031,"mergeCommit":{"message":"[CI]
Fix Renovate helper bot trigger and out of sync labels (#231031)\n\n##
Summary\n\nNote: I will backport this after backporting the original PR
#228664. I\nwas waiting to see the stability of the original
PR.\n\nFixes two issues:\n- The
[pipeline](https://buildkite.com/elastic/kibana-renovate-helper)\nis not
triggering for Renovate PRs, unless
explicitly\n[commenting](https://github.com/elastic/kibana/pull/230882#issuecomment-3165286181)\nto
run\n- Since we're passing along `GITHUB_PR_*` env variables to the
PR\npipeline. Labels added in the helper pipeline to the PR itself were
not\nin sync with the PR run. Example
[this\nrun](https://buildkite.com/elastic/kibana-pull-request/builds/327690#019885d3-196a-4950-896c-3bf7de6f735f)\nshould
have `ci:cloud-deploy`
label.","sha":"f61e1a2bb618c2f0f7586acb61721c76b0102674"}},{"url":"https://github.com/elastic/kibana/pull/231216","number":231216,"branch":"9.1","state":"OPEN"}]}]
BACKPORT-->
NicholasPeretti pushed a commit to NicholasPeretti/kibana that referenced this pull request Aug 18, 2025
…231031)

## Summary

Note: I will backport this after backporting the original PR elastic#228664. I
was waiting to see the stability of the original PR.

Fixes two issues:
- The [pipeline](https://buildkite.com/elastic/kibana-renovate-helper)
is not triggering for Renovate PRs, unless explicitly
[commenting](elastic#230882 (comment))
to run
- Since we're passing along `GITHUB_PR_*` env variables to the PR
pipeline. Labels added in the helper pipeline to the PR itself were not
in sync with the PR run. Example [this
run](https://buildkite.com/elastic/kibana-pull-request/builds/327690#019885d3-196a-4950-896c-3bf7de6f735f)
should have `ci:cloud-deploy` label.
qn895 pushed a commit to qn895/kibana that referenced this pull request Aug 26, 2025
…231031)

## Summary

Note: I will backport this after backporting the original PR elastic#228664. I
was waiting to see the stability of the original PR.

Fixes two issues:
- The [pipeline](https://buildkite.com/elastic/kibana-renovate-helper)
is not triggering for Renovate PRs, unless explicitly
[commenting](elastic#230882 (comment))
to run
- Since we're passing along `GITHUB_PR_*` env variables to the PR
pipeline. Labels added in the helper pipeline to the PR itself were not
in sync with the PR run. Example [this
run](https://buildkite.com/elastic/kibana-pull-request/builds/327690#019885d3-196a-4950-896c-3bf7de6f735f)
should have `ci:cloud-deploy` label.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

release_note:skip Skip the PR/issue when compiling release notes Team:Operations Kibana-Operations Team v8.17.10 v8.18.5 v8.19.2 v9.0.5 v9.1.2 v9.2.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants