[MCLEAN-78] Ability to retry longer if clean fails

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Auto Closed
• Affects Version/s: 3.0.0
• Environment: Windows 10, 64-bit, build 10.0.14393
• Assignee: Unassigned
• Reporter: Gili
• Created: 22/Nov/16 19:38
• Updated: 27/Dec/20 16:10
• Resolved: 27/Dec/20 16:10

Description

Following up on MCLEAN-45, I am running into a problem where a build fails to clean 100% of the time. The existing retry mechanism sleeps roughly 1 second, which makes it impossible to investigate what is actually holding the lock. I already went through the obvious culprits by disabling Windows Indexing and anti-virus, to no avail. I can reproduce the problem on two separate machines as well. I am afraid that Maven itself might be holding the lock.

I order to aid troubleshooting of this scenario, can you please add or enhance the existing configuration options so that the clean plugin can retry longer (e.g. up to 30 seconds)?

Worse-case scenario, the lock will eventually get released and my build will work. Best-case scenario, the lock won't get released but I will finally have enough time to run SysInternals ProcessMonitor to figure out who is holding the lock. When I try doing this after the JVM shuts down, I don't find anyone holding the lock so I strongly suspect the JVM itself is at fault.

Proposal: let users specify a max retry time and generate the intermediate sleep intervals on their behalf. I would happily use retry intervals of up to a minute if it meant that my automated builds would be more stable.

Issue Links

• relates to: MCLEAN-45 Clean plugin should support a silent retry in case the first attemp fails