dra: support bumping releases minor/patch using the existing tools

[v1v]

Motivation/summary

Honour #20355 so it can run the existing release automation already implemented using GitHub actions.

How it works can be found at https://github.com/elastic/apm-server/blob/main/dev_docs/RELEASES.md

In this case, we use a shell script to trigger the existing minor or patch github workflow based on the version, if it ends with 0 is a new minor, otherwise it's a patch release.

Use https://github.com/elastic/gh-cli-buildkite-plugin

Checklist

• Update CHANGELOG.asciidoc
• Documentation has been updated

For functional changes, consider:

• Is it observable through the addition of either logging or metrics?
• Is its use being published in telemetry to enable product improvement?
• Have system tests been added to avoid regression?

How to test these changes

As part of the Unified Release Process

Related issues

• add DRA version bump pipeline #20355
• And there is a relationship with a private GH Issue linked here too.

Implementation details

I enabled the PR bump automation creation using the existing automation that relies on some GH actions and makefiles. It's not migrated to BK for various reasons:

1. The existing automation has been there for quite some time.
2. The APM Server team is familiar with the current automation and can act if needed.
3. There is no easy support for GPG signing in Buildkite, while it's a requirement when pushing commits in this repository (verified commits branch protection).

[github-actions]

🤖 GitHub comments

Just comment with:

• run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

[mergify]

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

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

[v1v]

@ninalee12 , I'd assume this is about once those PRs are merged, then this should be unblocked, for now manually, correct?

[ninalee12]

Hey Victor, I think for now manually. 🤔

I'm assuming that after those PR steps are created + merged, the DRA artifacts would follow and be uploaded. Once that's completed, we can then unblock

[v1v]

I'm assuming that after those PR steps are created + merged, the DRA artifacts would follow and be uploaded

Correct, that's push-based and the DRA artifacts are generated as part of

apm-server/catalog-info.yaml

Lines 17 to 50 in b67261b

	---
	apiVersion: backstage.io/v1alpha1
	kind: Resource
	metadata:
	name: buildkite-pipeline-apm-server-package
	description: Buildkite Pipeline for packaging the APM Server
	links:
	- title: Pipeline
	url: https://buildkite.com/elastic/apm-server-package
	spec:
	type: buildkite-pipeline
	owner: group:obs-ds-intake-services
	system: buildkite
	implementation:
	apiVersion: buildkite.elastic.dev/v1
	kind: Pipeline
	metadata:
	name: apm-server-package
	spec:
	branch_configuration: "main 7.* 8.* 9.*"
	repository: elastic/apm-server
	pipeline_file: ".buildkite/package.yml"
	provider_settings:
	build_branches: true
	build_pull_requests: true
	build_tags: false
	filter_enabled: true
	filter_condition: >-
	build.pull_request.id == null || (build.creator.name == 'elasticmachine' && build.pull_request.id != null)
	cancel_intermediate_builds: true
	cancel_intermediate_builds_branch_filter: "!main !8.* !9.*"
	skip_intermediate_builds: true
	skip_intermediate_builds_branch_filter: "!main !8.* !9.*"

[v1v]

Thanks for confirming 🙇

[fr4nc1sc0-r4m0n]

LGTM

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: e484e5a

History

• 💚 Build #9764 succeeded 2f59c1d
• 💚 Build #9746 succeeded 8da920e
• 💚 Build #9660 succeeded 80b05f5

cc @v1v

[carsonip]

thank you