You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@airflow.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2019/07/20 18:47:00 UTC

[jira] [Commented] (AIRFLOW-5005) Kubernetes tests should be split to separate jobs

    [ https://issues.apache.org/jira/browse/AIRFLOW-5005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16889570#comment-16889570 ] 

ASF subversion and git services commented on AIRFLOW-5005:
----------------------------------------------------------

Commit 87150e26fb3912dadaaa50b073d5f95ad4df1b0a in airflow's branch refs/heads/v1-10-test from Jarek Potiuk
[ https://gitbox.apache.org/repos/asf?p=airflow.git;h=87150e2 ]

[AIRFLOW-5005] Split kubernetes tests into separate jobs


> Kubernetes tests should be split to separate jobs
> -------------------------------------------------
>
>                 Key: AIRFLOW-5005
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-5005
>             Project: Apache Airflow
>          Issue Type: Improvement
>          Components: ci
>    Affects Versions: 1.10.3, 2.0.0
>            Reporter: Jarek Potiuk
>            Priority: Major
>
> In the current setup, two modes of Kubernetes run are sequentially run in one job. This is not a good idea because locally installed minikube cluster must be shutdown cleanly before the next mode is executed. It's unnecessary and causes random failures. It can be avoided by running two Kubernetes jobs in parallel - one per node.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)