[CI][Backports] add integrations-backport-dispatch private pipeline for triggering backport creation by mrodm · Pull Request #20284 · elastic/integrations

mrodm · 2026-07-22T14:00:11Z

Proposed commit message

[CI][Backports] add integrations-backport-dispatch private pipeline

Move backport branch creation trigger from the public integrations pipeline
to a new private integrations-backport-dispatch pipeline, preventing failures
caused by public-to-private pipeline trigger restrictions in Buildkite.

The public integrations pipeline can fail to trigger the private
integrations-backport pipeline in some scenarios due to public→private
pipeline restrictions in Buildkite. This PR introduces a new dedicated
private pipeline (integrations-backport-dispatch) that reliably triggers
integrations-backport on merges to main.

WHAT:

New .buildkite/pipeline.backport-dispatch.yml: private pipeline that
runs check-backports-inventory and trigger-backport-create on pushes
to main when .backports.yml changes.
pipeline.yml: removed the trigger-backport-create step (moved to
dispatch pipeline); narrowed check-backports-inventory to PR-only since
the main-push case is now owned by the dispatch pipeline.
pipeline.backport.yml: added integrations-backport-dispatch as a
valid trigger source in the check-ui guard; added failure email
notifications scoped to automated runs from the dispatch pipeline.
trigger_backport.sh: added a safeguard that exits 1 if backport branch
creation is attempted from any pipeline other than
integrations-backport-dispatch.
catalog-info.yaml: registered the new pipeline as a Backstage resource.
pull-requests.json: added the new pipeline entry and
pipeline.backport-dispatch.yml to skip_ci_on_only_changed.
non_package_patterns.txt: added pipeline.backport-dispatch.yml so
changes to it alone do not trigger package integration tests.

WHY:
Buildkite restricts public pipelines from triggering private pipelines in
certain scenarios (e.g. fork builds, specific webhook configurations). By
moving the backport branch creation trigger to a private pipeline, we
eliminate that failure mode while keeping the dry-run validation in the
public integrations pipeline for PR builds.

An example of the failure this addresses can be seen in:
https://buildkite.com/elastic/integrations/builds/46280

Author's Checklist

Revert commit 0c3d9a6f47 ("Skip integrations tests - to be removed") before merging — it was added for testing purposes only.

Related issues

Closes backport: make branch creation PR-driven via .backports.yml #19211
Follow-up from [CI] Add automated backport changelog sync to main #19273

This PR was generated with the assistance of Claude (claude-sonnet-4-6).

…ing backport creation The public integrations pipeline can fail to trigger the private integrations-backport pipeline in some scenarios due to public→private pipeline restrictions in Buildkite. Move the backport branch creation trigger to a new dedicated private pipeline (integrations-backport-dispatch) that reliably triggers integrations-backport on merges to main. Changes: - Add .buildkite/pipeline.backport-dispatch.yml with inventory validation and backport creation trigger steps - Remove trigger-backport-create step from pipeline.yml; narrow check-backports-inventory to PR-only in that pipeline - Allow integrations-backport-dispatch as a valid trigger source in pipeline.backport.yml and add failure email notifications - Add pipeline slug safeguard in trigger_backport.sh so branch creation only runs from integrations-backport-dispatch - Register the new pipeline in catalog-info.yaml, pull-requests.json, and non_package_patterns.txt Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>

infra-vault-gh-plugin-prod · 2026-07-22T14:07:43Z

💚 Build Succeeded

Buildkite Build
Commit: b9fac20

cc @mrodm

mrodm · 2026-07-22T14:08:06Z

+    if: |
+      build.branch == "nonexisting"


To be reverted before merging

I guess this is some leftover?

Yes, I'll remove it before merging to avoid triggering a new step for each package defined in the repo (460 or more steps).

mrodm · 2026-07-22T14:09:52Z

+        if [[ "${BUILDKITE_PIPELINE_SLUG}" != "integrations-backport-dispatch" ]]; then
+            echo "Backport branch creation can only run from the 'integrations-backport-dispatch' pipeline (got: ${BUILDKITE_PIPELINE_SLUG})"
+            exit 1
+        fi


If this pipeline is triggered from main (and therefore it would create a new backport branch), it must be running from the new integrations-backport-dispatch pipeline.

mrodm · 2026-07-22T15:23:50Z

Hi @elastic/observablt-ci , adding you as a reviewers in case there is anything that should be changed or improved regarding the changes in Buildkite pipelines.
Thanks in advance!

mallendem · 2026-07-27T13:25:46Z

+    if: |
+      build.branch == "nonexisting"


I guess this is some leftover?

mallendem · 2026-07-27T13:28:52Z

+        build_tags: false
+        filter_enabled: true
+        filter_condition: >-
+          build.pull_request.id == null || (build.creator.name == 'elasticmachine' && build.pull_request.id != null && build.source == 'api')


If we don't build PRs, build.pull_request.id == null is always true, so the second part is never evaluated.

Just copied from the other catalog-info entries.
I did the same, just in case at some point it is updated to run in Pull Requests as a safe guard, even if it is not supposed to do so.

mallendem · 2026-07-27T13:30:19Z

+        ecosystem:
+          access_level: MANAGE_BUILD_AND_READ
+        everyone:
+          access_level: READ_ONLY


backport pipeline has

everyone: access_level: BUILD_AND_READ

Not against lowering the permissions, double checking to see if it is intended.

It's expected to have that value 👍
This would allow to run this pipeline for any user that merges Pull Requests in the integrations.

mrodm and others added 3 commits July 21, 2026 18:32

Skip integrations tests - to be removed

f8da308

split check-backports-inventory if condition onto two lines

b9fac20

mrodm self-assigned this Jul 22, 2026

mrodm commented Jul 22, 2026

View reviewed changes

mrodm marked this pull request as ready for review July 22, 2026 14:25

mrodm requested a review from a team as a code owner July 22, 2026 14:25

mrodm requested a review from a team July 22, 2026 14:25

mrodm mentioned this pull request Jul 24, 2026

[Docs][Backports] Update developer documentation to reflect new automated backport workflow (#19284) #20351

Draft

1 task

mallendem reviewed Jul 27, 2026

View reviewed changes

mrodm requested a review from mallendem July 27, 2026 15:55

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

[CI][Backports] add integrations-backport-dispatch private pipeline for triggering backport creation - #20284

[CI][Backports] add integrations-backport-dispatch private pipeline for triggering backport creation#20284
mrodm wants to merge 3 commits into
elastic:mainfrom
mrodm:create_new_dispatch_backport_pipeline

mrodm commented Jul 22, 2026 •

edited

Loading

Uh oh!

infra-vault-gh-plugin-prod Bot commented Jul 22, 2026

Uh oh!

mrodm Jul 22, 2026

Uh oh!

mallendem Jul 27, 2026

Uh oh!

mrodm Jul 27, 2026

Uh oh!

mrodm Jul 22, 2026

Uh oh!

mrodm commented Jul 22, 2026

Uh oh!

mallendem Jul 27, 2026

Uh oh!

mallendem Jul 27, 2026

Uh oh!

mrodm Jul 27, 2026

Uh oh!

mallendem Jul 27, 2026

Uh oh!

mrodm Jul 27, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

mrodm commented Jul 22, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Proposed commit message

Author's Checklist

Related issues

Uh oh!

infra-vault-gh-plugin-prod Bot commented Jul 22, 2026

💚 Build Succeeded

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

mrodm commented Jul 22, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

mrodm commented Jul 22, 2026 •

edited

Loading