fix(ci): use sed to update parent POM version instead of versions:update-parent#969
Draft
Copilot wants to merge 2 commits into
Draft
fix(ci): use sed to update parent POM version instead of versions:update-parent#969Copilot wants to merge 2 commits into
Copilot wants to merge 2 commits into
Conversation
The CI was failing because `mvn help:evaluate` requires the parent POM to be resolvable. When killbill-api references a parent version like 0.147.0-8d4551b-SNAPSHOT that doesn't exist in any accessible repository, the evaluate command fails with exit code 1. The fix moves `versions:update-parent` before `help:evaluate` so that the parent is updated to the locally-installed killbill-oss-parent version before Maven tries to resolve it.
Copilot created this pull request from a session on behalf of
xsalefter
June 6, 2026 14:52
View session
Contributor
|
@copilot still failing. Can you check? |
…ate-parent The versions:update-parent Maven goal fails when the currently declared parent POM is unresolvable (e.g. 0.147.0-8d4551b-SNAPSHOT not in any repository). Maven cannot even load the project model to start the goal. Replace with a sed command that directly edits the <version> inside the <parent> block of pom.xml. This eliminates the chicken-and-egg problem where Maven needs to resolve the old parent before it can update to the new one.
Contributor
Author
The root cause is that Fixed in 8a4e28b by replacing |
Copilot
AI
changed the title
fix(ci): update parent POM before evaluating project version
fix(ci): use sed to update parent POM version instead of versions:update-parent
Jun 6, 2026
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
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.
CI fails at "Download dependencies and setup the various pom.xml" because
mvn versions:update-parentrequires the parent POM to be resolvable before it can even start.killbill-apionjava2xdeclares parent0.147.0-8d4551b-SNAPSHOTwhich doesn't exist in any accessible repository — Maven cannot load the project model to execute the goal.Change
mvn versions:update-parentwith asedcommand that directly edits the<version>inside the<parent>block of each pom.xml. This eliminates the chicken-and-egg problem where Maven needs to resolve the old parent before it can update to the new one.Why other jobs in the same run succeeded
The failure is non-deterministic. It depends on whether Sonatype OSSRH snapshots still has the old parent artifact cached. Jobs that got a fast 404 failed immediately (attempt 1 postgresql: 1s); the mysql job hung for 60s on the wagon timeout before failing. Jobs where the snapshot repo happened to serve the artifact succeeded. This fix eliminates the external dependency entirely.