[
https://issues.apache.org/jira/browse/AIRFLOW-5077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16896908#comment-16896908
]
ASF subversion and git services commented on AIRFLOW-5077:
----------------------------------------------------------
Commit 00c5a1c39fed0a6324bb77922258d74a6c73b917 in airflow's branch
refs/heads/v1-10-test from Jarek Potiuk
[ https://gitbox.apache.org/repos/asf?p=airflow.git;h=00c5a1c ]
[AIRFLOW-5077] Skip force pulling latest python in CI environment (#5690)
The latest python will only be pulled by DockerHub when building
master/v1-10-test - which means that it will eventually catch
up with the latest python security releases but it will not
slow down the CI builds.
(cherry picked from commit 27c79582bae89120ab9f8bed62b064d6531b9968)
> CI builds gets slower when newer version of python gets released
> ----------------------------------------------------------------
>
> Key: AIRFLOW-5077
> URL: https://issues.apache.org/jira/browse/AIRFLOW-5077
> Project: Apache Airflow
> Issue Type: Improvement
> Components: ci
> Affects Versions: 1.10.4, 2.0.0
> Reporter: Jarek Potiuk
> Priority: Major
> Fix For: 1.10.4
>
>
> We are always pulling latest version of python when CI build is done - we
> should only do that on Dockerhub. This way we will start using the latest
> python version only after it's been built on Dockerhub (still the builds will
> catch up eventually!)
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
