potiuk commented on a change in pull request #6285: [AIRFLOW-XXX] Updates to 
Breeze documentation from GSOD
URL: https://github.com/apache/airflow/pull/6285#discussion_r334283907
 
 

 ##########
 File path: BREEZE.rst
 ##########
 @@ -62,6 +62,47 @@ Docker Compose
 
 - **Permissions**: Configure to run the ``docker-compose`` command.
 
+Docker Images Used by Breeze
+----------------------------
+
+For all development tasks, related integration tests and static code checks, 
we use Docker
+images maintained on the Docker Hub in the ``apache/airflow`` repository.
+
+There are three images that we are currently managing:
+
+* **Slim CI** image that is used for static code checks (size of ~500MB). Its 
tag follows the pattern
+  of ``<BRANCH>-python<PYTHON_VERSION>-ci-slim`` (for example, 
``apache/airflow:master-python3.6-ci-slim``).
+  The image is built using the `<Dockerfile>`_ Dockerfile.
+* **Full CI image*** that is used for testing. It contains a lot more 
test-related installed software
+  (size of ~1GB). Its tag follows the pattern of 
``<BRANCH>-python<PYTHON_VERSION>-ci``
+  (for example, ``apache/airflow:master-python3.6-ci``). The image is built 
using the
+  `<Dockerfile>`_ Dockerfile.
+* **Checklicence image** that is used during license check with the Apache RAT 
tool. It does not
+  require any of the dependencies that the two CI images need so it is built 
using a different Dockerfile
+  `<Dockerfile-checklicence>`_ and only contains Java + Apache RAT tool. The 
image is
+  labelled with ``checklicence``, for example: 
``apache/airflow:checklicence``. No versioning is used for
+  the Checklicence image.
+
+We also use a very small `<Dockerfile-context>`_ Dockerfile to fix file 
permissions
 
 Review comment:
   This paragraph can be removed. The Dockefile-context is removed already.

----------------------------------------------------------------
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:
us...@infra.apache.org


With regards,
Apache Git Services

Reply via email to