ci(release): force Maven to IPv4 and skip tests on release deploy#1983
Merged
jfallows merged 3 commits intoJul 2, 2026
Conversation
maven.packages.aklivity.io publishes an AAAA record whose IPv6 endpoint is not routable from GitHub-hosted runners, so dependency downloads fail with "Network is unreachable" when the JVM tries the IPv6 address. Set MAVEN_OPTS -Djava.net.preferIPv4Stack=true at the workflow level so all mvnw invocations use the reachable IPv4 address. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01C5bGVS9PYHAbXzqiHZDXie
The release deploy re-ran the full test suite; those tests already run in the build workflow, so skip them here for faster releases. This also avoids the k3po IPv6 spec tests (which bind [::1] in the Maven JVM) conflicting with the -Djava.net.preferIPv4Stack workaround needed for the package repo download. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01C5bGVS9PYHAbXzqiHZDXie
jfallows
changed the title
… stack -Djava.net.preferIPv4Stack=true fixed the release deploy's unreachable AAAA record for maven.packages.aklivity.io, but it disables the JVM's IPv6 stack entirely, which build.yml cannot tolerate since it runs the k3po IT suite (including IPv6 loopback tests that bind [::1]). Replace it with a transient /etc/hosts entry that pins only that hostname to its IPv4 address, leaving the JVM's IPv6 stack untouched. Apply to build, codeql (scan) and release so all three stop depending on IPv6 reachability to that host. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01C5bGVS9PYHAbXzqiHZDXie
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
2 participants
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.
Description
Mainline (
develop) companion covering two release-workflow fixes:Force Maven to IPv4 — set
MAVEN_OPTS: -Djava.net.preferIPv4Stack=trueat the workflow level.maven.packages.aklivity.iopublishes an AAAA (IPv6) record (2a12:5240::1) whose endpoint isn't routable from GitHub-hosted runners, so dependency downloads failed with "Network is unreachable"; forcing IPv4 uses the reachable89.106.200.1.Skip tests on release deploy — add
-DskipTeststoDeploy via Maven. Those tests already run inbuild.ymlCI, so this makes releases faster and avoids the k3po IPv6 spec tests (which bind[::1]inside the Maven JVM) conflicting with thepreferIPv4Stackworkaround above.Note: the real fix for (1) is infra-side (drop/repair the AAAA record if the IPv6 endpoint isn't served); this is a reliable runner-side workaround in the meantime.
No associated issue.
🤖 Generated with Claude Code