Skip to content

release-step-3

release-step-3 #26

Manually triggered January 21, 2026 13:07
Status Success
Total duration 46m 12s
Artifacts

release-step-3.yml

on: workflow_dispatch
validate-tag
29s
validate-tag
Wait for artifacts to be available on maven central
22m 36s
Wait for artifacts to be available on maven central
Deploy to Maven Central (Buildkite)
17m 39s
Deploy to Maven Central (Buildkite)
Publish AWS Lambda
4m 10s
Publish AWS Lambda
Create GitHub Release
17m 44s
Create GitHub Release
Bump versions and create PR  /  validate-tag
5s
Bump versions and create PR / validate-tag
Build and push docker images
51s
Build and push docker images
Bump versions and create PR  /  Bump versions and create PR
37s
Bump versions and create PR / Bump versions and create PR
Fit to window
Zoom out
Zoom in

Annotations

3 warnings and 1 notice
Publish AWS Lambda
No files were found with the provided path: .ci/.arn-file.md. No artifacts will be uploaded.
notify
Additionally, the attachment-level `fallback` argument is missing in the request payload for a chat.postMessage call - To avoid this warning, it is recommended to always provide a top-level `text` argument when posting a message. Alternatively, you can provide an attachment-level `fallback` argument, though this is now considered a legacy field (see https://api.slack.com/reference/messaging/attachments#legacy_fields for more details).
notify
The top-level `text` argument is missing in the request payload for a chat.postMessage call - It's a best practice to always provide a `text` argument when posting a message. The `text` is used in places where the content cannot be rendered such as: system push notifications, assistive technology such as screen readers, etc.
Buildkite Build URL
https://buildkite.com/elastic/apm-agent-java-release/builds/45