potiuk commented on a change in pull request #4543: [AIRFLOW-3718] [WIP] 
Multi-layered version of the docker image
URL: https://github.com/apache/airflow/pull/4543#discussion_r262153105
 
 

 ##########
 File path: .travis.yml
 ##########
 @@ -19,26 +19,30 @@
 sudo: true
 dist: trusty
 language: python
-python:
-  - "3.6"
 env:
   global:
-    - DOCKER_COMPOSE_VERSION=1.20.0
-    - TRAVIS_CACHE=$HOME/.travis_cache/
+    - DOCKER_COMPOSE_VERSION=1.23.2
   matrix:
-    - TOX_ENV=py27-backend_mysql-env_docker
-    - TOX_ENV=py27-backend_sqlite-env_docker
-    - TOX_ENV=py27-backend_postgres-env_docker
-    - TOX_ENV=py35-backend_mysql-env_docker PYTHON_VERSION=3
-    - TOX_ENV=py35-backend_sqlite-env_docker PYTHON_VERSION=3
-    - TOX_ENV=py35-backend_postgres-env_docker PYTHON_VERSION=3
-    - TOX_ENV=py27-backend_postgres-env_kubernetes KUBERNETES_VERSION=v1.9.0
-    - TOX_ENV=py35-backend_postgres-env_kubernetes KUBERNETES_VERSION=v1.10.0 
PYTHON_VERSION=3
-
+    - BACKEND=mysql ENV=docker
+    - BACKEND=postgres ENV=docker
+    - BACKEND=sqlite ENV=docker
+    - BACKEND=postgres ENV=kubernetes KUBERNETES_VERSION=v1.9.0
+    - BACKEND=postgres ENV=kubernetes KUBERNETES_VERSION=v1.10.0
+python:
+  - "3.6"
+  - "3.5"
 
 Review comment:
   My current approach (still testing it) is that yes - all the tests will be 
run in docker, same way they were run before. The main difference is that we 
prepare locally a final image that can be run for testing - from the current 
sources, utilising docker layers and registry as cache rather than .pip-cache 
adn .wheels directories mounted from the host. This is a bit cleaner and 
hopefully I can make it equally fast or even faster. 
   
   I am still looking at some limitation and speed there so this might change 
if I find I cannot do it as good as with folder/sources/wheel/.pip_cache 
caching.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

Reply via email to