This is an automated email from the ASF dual-hosted git repository.

potiuk pushed a commit to branch v1-10-test
in repository https://gitbox.apache.org/repos/asf/airflow.git

commit 43e51e48c202d827303553ef8f878e688358bb11
Author: Kaxil Naik <[email protected]>
AuthorDate: Fri Oct 9 08:57:51 2020 +0100

    Use only-if-needed upgrade strategy for PRs (#11363)
    
    Currently, upgrading dependencies in setup.py still runs with previous 
versions of the package for the PR which fails.
    
    This will change to upgrade only the package that is required for the PRs
    
    (cherry picked from commit 7f674c685d8b95787c52af15e359de7053a8bf67)
---
 Dockerfile.ci | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/Dockerfile.ci b/Dockerfile.ci
index 02a9a53..122c5e2 100644
--- a/Dockerfile.ci
+++ b/Dockerfile.ci
@@ -294,15 +294,14 @@ ENV 
UPGRADE_TO_LATEST_CONSTRAINTS=${UPGRADE_TO_LATEST_CONSTRAINTS}
 # The goal of this line is to install the dependencies from the most current 
setup.py from sources
 # This will be usually incremental small set of packages in CI optimized 
build, so it will be very fast
 # In non-CI optimized build this will install all dependencies before 
installing sources.
-# Usually we will install versions constrained to the current constraints file
+# Usually we will install versions based on the dependencies in setup.py and 
upgraded only if needed.
 # But in cron job we will install latest versions matching setup.py to see if 
there is no breaking change
 # and push the constraints if everything is successful
 RUN \
     if [[ "${UPGRADE_TO_LATEST_CONSTRAINTS}" != "false" ]]; then \
         pip install -e ".[${AIRFLOW_EXTRAS}]" --upgrade --upgrade-strategy 
eager; \
     else \
-        pip install -e ".[${AIRFLOW_EXTRAS}]" \
-            --constraint "${AIRFLOW_CONSTRAINTS_URL}" ; \
+        pip install -e ".[${AIRFLOW_EXTRAS}]" --upgrade --upgrade-strategy 
only-if-needed; \
     fi
 
 # Copy all the www/ files we need to compile assets. Done as two separate COPY

Reply via email to