CI/CD: Maven wrapper download failures causing build instability
Open
Nobody has claimed this yet.
dotCMS : Build
dotCMS : Technical Debt
github_actions
Priority : 2 High
Team : Platform
- Dominant language
- Java
- Stars
- 970
- Forks
- 486
- Avg merge
- 3d 33m
- Merged PRs (30d)
- 170
Description
Description
Maven wrapper downloads from external Apache repository are causing CI/CD build failures due to transient network issues or rate limiting. This affects build reliability and developer productivity.
Problem Description:
- External downloads from repo.maven.apache.org fail intermittently
- Specific files: apache-maven-3.9.2-bin.zip and maven-wrapper-3.2.0.jar
- GitHub Actions uses clean machines without wrapper cache
- Failures appear to be network-related (timeouts, rate limiting)
Impact:
- Unpredictable CI/CD build failures
- Developer workflow interruptions
- Build reliability issues
Proposed Solutions:
- Mirror wrapper files to repo.dotcms.com for reliability
- Implement GitHub Actions caching for ~/.m2/wrapper/dists
- Consider wrapper version upgrades if stability improves
Acceptance Criteria
- [Define what needs to be accomplished]
Additional Notes
[Any additional context or notes]
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source files or tests are named. Start with the repository's GitHub Actions workflows and Maven wrapper configuration, then inspect how ~/.m2/wrapper/dists is populated on clean runners. Clarify which proposed mitigation is required and define an acceptance test for reliable downloads of apache-maven-3.9.2-bin.zip and maven-wrapper-3.2.0.jar.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, java
- Domain
- build-system, ci-cd
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100