[jira] [Updated] (PHOENIX-6102) Better isolation for CI jobs an ASF Jenkins

["Istvan Toth (Jira)" <ji...@apache.org>]

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

Istvan Toth updated PHOENIX-6102:
---------------------------------
    Attachment: PHOENIX-6102.4.x.v1.patch

> Better isolation for CI jobs an ASF Jenkins
> -------------------------------------------
>
>                 Key: PHOENIX-6102
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-6102
>             Project: Phoenix
>          Issue Type: Improvement
>            Reporter: Istvan Toth
>            Assignee: Istvan Toth
>            Priority: Major
>         Attachments: PHOENIX-6102.4.x.v1.patch, PHOENIX-6102.master.v1.patch
>
>
> Currently we are running the CI jobs on ASF infrastructure as simple unix applications, and are sharing the machines with different projects (and different instances of our jobs).
> This results in quite a few problems:
>  * Clobbering other jobs/getting clobbered by buggy cleanup efforts in scripts
>  * Causing/Suffering from resource starvation
>  * Conflicts in shared maven local repositories (f.e. HBase recompile)
> The obvious solution to (some) of these problems is utilising Jenkins's docker support. 
> One problem with that approach is that we lose the efficiency of a persistent local maven repo as a cache. We may try to modify the maven setup to use that, or we can accept the performance hit, considering that our jobs are very long, so the additional time/traffic generated is not a deal breaker.



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