[ 
https://issues.apache.org/jira/browse/HDDS-5772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Attila Doroszlai updated HDDS-5772:
-----------------------------------
    Description: 
CI workflow uses Maven build cache to save some time.  We use a unique cache 
name for each check to avoid concurrency issues.  This may cause problems 
because each repository is limited to 5GB of caches.  So it is possible that 
too many distinct caches cause unnecessary eviction.

Another problem is that cache is built on top of previous versions, so we keep 
including obsolete dependencies:

{code}
com/fasterxml/jackson/core/jackson-annotations/2.10.5/jackson-annotations-2.10.5.jar
com/fasterxml/jackson/core/jackson-annotations/2.12.1/jackson-annotations-2.12.1.jar
com/fasterxml/jackson/core/jackson-annotations/2.9.10/jackson-annotations-2.9.10.jar
com/fasterxml/jackson/core/jackson-core/2.10.5/jackson-core-2.10.5.jar
com/fasterxml/jackson/core/jackson-core/2.12.1/jackson-core-2.12.1.jar
com/fasterxml/jackson/core/jackson-core/2.9.10/jackson-core-2.9.10.jar
...
org/apache/commons/commons-lang3/3.4/commons-lang3-3.4.jar
org/apache/commons/commons-lang3/3.5/commons-lang3-3.5.jar
org/apache/commons/commons-lang3/3.7/commons-lang3-3.7.jar
org/apache/commons/commons-lang3/3.8.1/commons-lang3-3.8.1.jar
{code}

  was:CI workflow uses Maven build cache to save some time.  We use a unique 
cache name for each check to avoid concurrency issues.  This may cause problems 
because each repository is limited to 5GB of caches.  So it is possible that 
too many distinct caches cause unnecessary eviction.


> Improve Maven caching in CI
> ---------------------------
>
>                 Key: HDDS-5772
>                 URL: https://issues.apache.org/jira/browse/HDDS-5772
>             Project: Apache Ozone
>          Issue Type: Improvement
>          Components: build
>            Reporter: Attila Doroszlai
>            Assignee: Attila Doroszlai
>            Priority: Major
>
> CI workflow uses Maven build cache to save some time.  We use a unique cache 
> name for each check to avoid concurrency issues.  This may cause problems 
> because each repository is limited to 5GB of caches.  So it is possible that 
> too many distinct caches cause unnecessary eviction.
> Another problem is that cache is built on top of previous versions, so we 
> keep including obsolete dependencies:
> {code}
> com/fasterxml/jackson/core/jackson-annotations/2.10.5/jackson-annotations-2.10.5.jar
> com/fasterxml/jackson/core/jackson-annotations/2.12.1/jackson-annotations-2.12.1.jar
> com/fasterxml/jackson/core/jackson-annotations/2.9.10/jackson-annotations-2.9.10.jar
> com/fasterxml/jackson/core/jackson-core/2.10.5/jackson-core-2.10.5.jar
> com/fasterxml/jackson/core/jackson-core/2.12.1/jackson-core-2.12.1.jar
> com/fasterxml/jackson/core/jackson-core/2.9.10/jackson-core-2.9.10.jar
> ...
> org/apache/commons/commons-lang3/3.4/commons-lang3-3.4.jar
> org/apache/commons/commons-lang3/3.5/commons-lang3-3.5.jar
> org/apache/commons/commons-lang3/3.7/commons-lang3-3.7.jar
> org/apache/commons/commons-lang3/3.8.1/commons-lang3-3.8.1.jar
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to