Repository navigation
release-step-3 #33
release-step-3.yml
on: workflow_dispatch
validate-tag
31s
Wait for artifacts to be available on maven central
26m 47s
Bump versions and create PR
/
Bump versions and create PR
notify
6s
Annotations
5 errors, 3 warnings, and 1 notice
|
Deploy to Maven Central (Buildkite)
Process completed with exit code 2.
|
|
Deploy to Maven Central (Buildkite)
Process completed with exit code 1.
|
|
Wait for artifacts to be available on maven central
The run was canceled by @SylvainJuge.
|
|
Wait for artifacts to be available on maven central
The operation was canceled.
|
|
release-step-3
The run was canceled by @SylvainJuge.
|
|
Wait for artifacts to be available on maven central
Unexpected input(s) 'maven-central', 'sonatype-central', valid inputs are ['artifact-id', 'group-id', 'version']
|
|
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://docs.slack.dev/legacy/legacy-messaging/legacy-secondary-message-attachments 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/51
|