Delegate the bump automation to the consumers rather than using a centralised bump automation.
For such it uses an opinionated approach where the current active branches and their snapshot manifests are published to a Google bucket. The original information is defined in the artifacts-api but it requires some jq/bash manipulations hence it has been simplified so consumers can curl any given branch to know the latest built artifact.
Motivation/summary
Delegate the bump automation to the consumers rather than using a centralised bump automation.
For such it uses an opinionated approach where the current active branches and their snapshot manifests are published to a Google bucket. The original information is defined in the
artifacts-api
but it requires some jq/bash manipulations hence it has been simplified so consumers can curl any given branch to know the latest built artifact.Issues
Requires https://github.com/elastic/apm-pipeline-library/pull/2070
Further details
See https://github.com/elastic/apm-pipeline-library/pull/2069
https://github.com/elastic/apm-integration-testing/pull/1549 was created using the old fashion way
Test
I used my forked repo and changed the updatecli pipeline:
so I ran
and it created the PR -> https://github.com/v1v/apm-integration-testing/pull/3