You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Jarek Potiuk (Jira)" <ji...@apache.org> on 2019/10/18 08:53:00 UTC

[jira] [Resolved] (AIRFLOW-5649) Skipping tests for non relevant changes

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

Jarek Potiuk resolved AIRFLOW-5649.
-----------------------------------
    Fix Version/s: 2.0.0
       Resolution: Fixed

> Skipping tests for non relevant changes
> ---------------------------------------
>
>                 Key: AIRFLOW-5649
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-5649
>             Project: Apache Airflow
>          Issue Type: Improvement
>          Components: ci
>    Affects Versions: 2.0.0
>            Reporter: Jarek Potiuk
>            Assignee: Jarek Potiuk
>            Priority: Major
>             Fix For: 2.0.0
>
>
> We can skip running tests for some changes that are not relevant:
> All the tests will always run for direct pushes. This will run all tests in master branch and v1-10-tests always (no matter if they are cron job or not).
> For PRs it works like that:
>  * if there are no changes in .py files -> the separate pylint check will be skipped altogether (pre-commit will skip the checks anyway in this case but we save time to pull/build images).
>  * if there is no change in .py .js .html . all unit tests will be skipped
>  * if there is a change in .py .js .html files but no kubernetes/* nor tests/kubernetes/* nor airflow/www/.* the Kubernetes unit tests will be skipped
> We still run all test in CRON on master so in case of any false negatives we will catch them anyway.
>  



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