wallentx commented on issue #496:
URL: https://github.com/apache/maven-mvnd/issues/496#issuecomment-2263745033

   This would be extremely useful for us in the context of running this in k8s. 
   Our monorepo CI has hit the limits. We are pulling down 1TB of dependencies 
and plugins per day, and are getting rate limited by public maven repos. If we 
switch to our private artifactory cloud as a pull-through cache, we're going to 
have to eat the transfer cost.
   
   We use the github actions ARC controller, so our runners spin up as pods in 
our cluster.
   If mavend could be deployed as a persistent k8s daemonset that holds a 
centralized .m2 cache, and the client runner pods simply sent a "execute goal" 
payload to the daemon, that would solve just about every (self-induced) problem 
we are currently trying to overcome.
   
   I suppose I'm just commenting here because it's nice to daydream. Back to 
trying to figure out why my builds wont use the .m2 cache on my build container 
🙃


-- 
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

Reply via email to