jira-importer commented on issue #149: URL: https://github.com/apache/maven-install-plugin/issues/149#issuecomment-2771841131
**[Tibor Digana](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=tibor17)** commented [Geoff Simpson](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=gsimpson) If you often see this issue and you have multithreaded build system, it means you have the problem of design because you have a common local repo. In my experiences this has nevere happened because every run of job in Jenkins was designed in Groovy Jenkinsfile in the way that local repositories were isolated in each run. Therefore no shared artifacts across builds and jobs, which is the best practice. I don't think the file locking is the way still because shared artifacts of jobs and builds override artifacts of your current job by foreign job and the build shows you fake result. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
