incubator-ivy-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gilles Scokart (JIRA)" <j...@apache.org>
Subject [jira] Commented: (IVY-321) cache and repository cleaning
Date Wed, 10 Jan 2007 09:39:27 GMT

    [ https://issues.apache.org/jira/browse/IVY-321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463509
] 

Gilles Scokart commented on IVY-321:
------------------------------------

Note that if the a clean-cache task is provided, the implementation should also consider the
http proxy.  If the user is asking to clean his cache, he should implicitely use the cache
of his proxy on the first request he does.  

The cache should keep a trace of which modules has been cleaned from the cache.  Whenthe first
http request is done for a cleaned module, the http header max-age should be set to 0 so that
the cache of the proxy is not used. (see also IVY-380)

> cache and repository cleaning
> -----------------------------
>
>                 Key: IVY-321
>                 URL: https://issues.apache.org/jira/browse/IVY-321
>             Project: Ivy
>          Issue Type: New Feature
>            Reporter: Gilles Scokart
>         Assigned To: Xavier Hanin
>
> Ivy should provide some solution to manage the size of the cache (and of repositories).
 Ivy configuration should have some rules saying how long to keep versions of the jars in
the cache.  Theses rules could be parametrized in function of the module, of the type of revision,
of the age of the files or depending of the last time it has been used, the existence of dependent
modules, etc.  (I let you choose the best solutions)
> The same kind of things should also exist for a reposiotry (mainly for continuous build
repository).
> The cleaning might be performed automatically when a retrieve (for the cache) or a publish
(for a repository) is performed, or might be invocable from a dedicated task.
> There is currently no easy way to perform similar cleaning.  
> To illustrate this need, here is a mail I received from a developper who is using ivy
since 1 day. He have wriiten an ant scripts launching some tests build by our continuous build.
> {quote}
> Gilles,
>  
> The build file is working great, so thanks for that! It's a very easy way to distribute
software to the testers (until now I had to send all the jars and update them manually etc)
>  
> However, one minor issue: I've noticed that ivy keeps all version in its cache. After
just a day of playing around with it I already got a cache of almost 100MB, so this will get
out of control rather quickly. Is there a configuration option somewhere to limit the cache
size? or to automatically delete older versions? Even if it just leaves the latest version
I'm ok with that, although it might be neat to leave the last 3 or 5 or something.
>   
> Peter
> {quote}

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message