sekikn commented on pull request #663: URL: https://github.com/apache/bigtop/pull/663#issuecomment-686363738
Yes, I think we can leverage this feature to mounting the .m2 directory for avoiding the network timeout. It will also speed up the CI. But I have a few concerns: * When multiple containers share the same .m2 directory of their host, what happens if they try to write into the same file simultaneously? * If a file in .m2 is broken by a network issue or something, do succeeding builds continue to fail unless the corrupted file is removed? (Maybe we need a new Jenkins job that finds and removes corrupted jars in .m2?) I'll investigate the above concerns and try to enable the .m2 mount on Jenkins when I have some time :) ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected]
