Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions .gitlab-ci.yml
Original file line number Diff line number Diff line change
Expand Up @@ -1238,6 +1238,7 @@ deploy_to_maven_central:
# Do not deploy release candidate versions
- if: '$CI_COMMIT_TAG =~ /^v[0-9]+\.[0-9]+\.[0-9]+$/'
when: on_success
allow_failure: true

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Disable artifact download for failed Maven deploy

With this rule the tag deploy can finish as an allowed failure, but verify_maven_central_deployment still uses needs: [ deploy_to_maven_central ], which defaults to downloading artifacts, while deploy_to_maven_central only uploads its artifacts on success. In the rerun/“release already exists” path this is meant to unblock, a failed deploy has no successful artifact archive, so the verify job can fail before its script reads OVERRIDE_MAVEN_VERIFY and the publishing gate remains blocked; make the verify need use artifacts: false or otherwise upload artifacts on failure.

Useful? React with 👍 / 👎.

- when: manual
allow_failure: true
script:
Expand Down
Loading