-
-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Streamline Maven versions across the infrastructure #4110
Comments
I doubt any of those have a reason not to be on the latest. |
Update: the only "critical" Maven old version in this issue is the one in Since we have #4135 preparing a major JDK upgrade in this Docker image, we should bump Maven version first. Proposal: @jayfranco999 and I will work on this with the following tasks:
|
Update for https://github.com/jenkins-infra/docker-packaging:
|
|
Update: -Weekly release of Jenkins used Maven 3.9.7 with success
|
Most of the Jenkins infrastructure assets using Maven are automated enough to get latest versions of Maven when available, as you can see in #4109.
However we still have old Maven versions which should either removed, commented (to explain why not using latest version) or upgraded:
jenkinsciinfra/packaging
Docker image (source in jenkins-infra/docker-packaging) use to build and release Jenkins Core still uses a3.8.6
version of Maven: https://github.com/jenkins-infra/docker-packaging/blob/6e66c994d26563e0fa7a6f8e7b52842d6bee974e/Dockerfile#L109These changes must be discussed with their author or usual maintainers!
The text was updated successfully, but these errors were encountered: