potiuk commented on PR #28979:
URL: https://github.com/apache/airflow/pull/28979#issuecomment-1398907022

   > I have a look and also found that we have environment variable 
USE_AIRFLOW_VERSION but we explicit set it to "wheel" (maybe somewhere in the 
past it make sense). We could use it for generate message or skip message if 
set to None. I plan to have a look more detail tomorrow
   
   I believe this is correct (but would be great to verify the logic - so 
please take a look) - in a number of steps in CI we install airflow and 
providers from pre-built wheels (to simulate the behaviour of installing wheels 
from PyPI)
   
   See: 
https://github.com/apache/airflow/blob/main/IMAGES.rst#building-docker-images-from-current-sources
   
   ```
   Building docker images from current sources
   ===========================================
   
   The easy way to build the CI/PROD images is to use `<BREEZE.rst>`_. It uses 
a number of optimization
   and caches to build it efficiently and fast when you are developing Airflow 
and need to update to
   latest version.
   
   CI image, airflow package is always built from sources. When you execute the 
image, you can however use
   the ``--use-airflow-version`` flag (or ``USE_AIRFLOW_VERSION`` environment 
variable) to remove
   the preinstalled source version of Airflow and replace it with one of the 
possible installation methods:
   
   * "none" airflow is removed and not installed
   * "wheel" airflow is removed and replaced with "wheel" version available in 
dist
   * "sdist" airflow is removed and replaced with "sdist" version available in 
dist
   * "<VERSION>" airflow is removed and installed from PyPI (with the specified 
version)
   
   For PROD image by default production image is built from the latest sources 
when using Breeze, but when
   you use it via docker build command, it uses the latest installed version of 
airflow and providers.
   However, you can choose different installation methods as described in
   `Building PROD docker images from released PIP packages 
<#building-prod-docker-images-from-released-packages>`_.
   Detailed reference for building production image from different sources can 
be found in:
   `Build Args reference 
<docs/docker-stack/build-arg-ref.rst#installing-airflow-using-different-methods>`_
   
   You can build the CI image using current sources this command:
   ```


-- 
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.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to