fix(ci): fix waitMaxTime unit and handle already-published artifacts#48
Merged
pratyush618 merged 1 commit intomainfrom Mar 29, 2026
Merged
fix(ci): fix waitMaxTime unit and handle already-published artifacts#48pratyush618 merged 1 commit intomainfrom
pratyush618 merged 1 commit intomainfrom
Conversation
- Change waitMaxTime from 30 to 1800 (unit is seconds, not minutes; 30 was below the 1800s minimum and silently ignored by the plugin) - Add ignorePublishedComponents=true to skip artifacts that were already published in a prior run (fixes "Component already exists" error when re-running the release workflow)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
waitMaxTimefrom30to1800— the unit is seconds, not minutes.30was below the plugin's 1800s minimum and silently ignored.ignorePublishedComponents=truetocentral-publishing-maven-plugin— the BOM0.1.0was already published in a prior run, causing "Component already exists" errors on re-deploy. This plugin-native option skips already-published components.Changes
pom.xml— update central-publishing-maven-plugin configagenteval-bom/pom.xml— same updateTest plan
0.1.0tag after merge