Details
-
New Feature
-
Status: Closed
-
Major
-
Resolution: Not A Bug
-
waiting-for-feedback
-
None
-
None
Description
Our CI solution is based on K8s. All builds happen in a worker pod created from scratch and will be reclaimed once job completes. When the CI worker pod is created, a dir path on the host (which the pod belongs) will be mounted to the pod which serves as the shared maven repo path to reduce downloads.
The current problem we are facing is:
- As multiple projects build shared the same maven repo path, when some project executes mvn install, artifacts will be installed to local maven repo. The artifacts installed might be having some issues and are inconsistent with the artifacts in remote repo, which would pollute the Maven shared cache and affect other builds.
We expect to support:
- Support two local repos, one is the shared local repo which is for downloading all artifacts from remote repo, and the other is the application level maven local repo where all project artifacts will be installed to.
- When the install command is executed, the artifacts built will be written into the application level maven local repo and will never pollute the shared one.
Is this currently possible? I don't find any useful doc or guide could solve the polluted cache issue.