Trigger ingest-dev release pipelines from version-bump automation

[fr4nc1sc0-r4m0n]

Summary

• Add triggers to ingest-dev-pipeline-release-minor-major and ingest-dev-pipeline-release-patch
• Keep the existing DRA approval block step and DRA polling afterward
• Scope the bump to REPOSITORY=fleet-server and map orchestrator WORKFLOW/NEW_VERSION

Test plan

• Run fleet-server-version-bump with WORKFLOW=patch and confirm the ingest-dev patch pipeline is triggered
• Confirm the original block step still appears and gates DRA fetch
• Confirm DRA json-watcher runs only after unblock

Related PRs

• beats: Trigger ingest-dev release pipelines from version-bump automation beats#52237
• elastic-agent: Trigger ingest-dev release pipelines from version-bump automation elastic-agent#15811
• fleet-server: Trigger ingest-dev release pipelines from version-bump automation #7457

[mergify]

This pull request does not have a backport label. Could you fix it @fr4nc1sc0-r4m0n? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-./d./d is the label to automatically backport to the 8./d branch. /d is the digit
• backport-active-all is the label that automatically backports to all active branches.
• backport-active-8 is the label that automatically backports to all active minor branches for the 8 major.
• backport-active-9 is the label that automatically backports to all active minor branches for the 9 major.

[v1v]

LGTM, let's wait for confirming the downstream BK pipeline is merged

[github-actions]

TL;DR

The Buildkite failure is not a code regression from this PR; the provided job log only contains cleanup/teardown output and a final non-zero exit, so the primary failing error is missing. Immediate action: re-run the :gcloud: Cloud e2e FIPS Test step and capture the failing section before cleanup.

Remediation

• Re-run build 15939 (or re-run just :gcloud: Cloud e2e FIPS Test) to rule out transient cloud/E2E instability.
• If it fails again, capture full output around mage test:cloudE2ERun from .buildkite/scripts/cloud_e2e_test.sh and confirm whether failure happened in test execution (line 48) or earlier setup checks (for example empty FLEET_SERVER_URL at lines 35-45).

Investigation details

Root Cause

The only failing job is :gcloud: Cloud e2e FIPS Test, but the available log file (/tmp/gh-aw/buildkite-logs/fleet-server-gcloud-cloud-e2e-fips-test.txt) does not include the original error. It only shows Terraform cleanup/destruction and then process exit:

• Log shows teardown (Destroy complete! Resources: 1 destroyed.) followed by:
  • 🚨 Error: The command exited with status 1
  • user command error: exit status 1
• This matches the trap-based cleanup flow in .buildkite/scripts/cloud_e2e_test.sh where cleanup always runs on exit (trap cleanup EXIT INT TERM, lines 17-29), so the real failure occurred earlier than what is present in this artifact.

PR scope check:

• Failed commit fec0534ae78346b3be84f5f3af4c03a892b2105f modifies only .buildkite/pipeline.version-bump.yaml.
• No service/runtime Go code changes were introduced by this commit.

Evidence

• Build: https://buildkite.com/elastic/fleet-server/builds/15939
• Job/step: :gcloud: Cloud e2e FIPS Test
• Key log excerpt:

Destroy complete! Resources: 1 destroyed.
^^^ +++
🚨 Error: The command exited with status 1
^^^ +++
user command error: exit status 1

• Relevant script paths:
  • .buildkite/scripts/cloud_e2e_test.sh#L17-L29 (cleanup trap)
  • .buildkite/scripts/cloud_e2e_test.sh#L47-L49 (cloud E2E execution)

Verification

• Not run locally (cloud Buildkite-only environment and provided artifact already truncated to teardown output).

Follow-up

• I checked for an existing flaky-test issue match for this exact failure signature but could not confirm one from the available data/integrity-filtered results.

---

What is this? | From workflow: PR Buildkite Detective

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.

[fr4nc1sc0-r4m0n]

please @elastic/elastic-agent-control-plane, @lorienhu and @blakerouse can you review this?