turbaszek opened a new pull request #14777:
URL: https://github.com/apache/airflow/pull/14777


   This change adds simple tool to verify that all expected files
   are present in airflow svn when doing release. Also in case
   of providers/backport releases it generates simple dockerfile
   that can be used to verify installation.
   
   ## Backports
   ```
   ➜ python check_files.py -v 2021.3.17rc1 -t backports -p ~/code/airflow_svn
   All sources: apache-airflow-backport-providers-2021.3.17rc1
       - sources .*\.asc$: OK
       - sources .*\.sha512$: OK
       - sources .*\.(whl|gz)$: OK
   
   apache.cassandra
       - sources .*\.asc$: OK
       - sources .*\.sha512$: OK
       - sources .*\.(whl|gz)$: OK
       - wheel .*\.asc$: OK
       - wheel .*\.sha512$: OK
       - wheel .*\.(whl|gz)$: OK
   
   ...
   
   zendesk
       - sources .*\.asc$: OK
       - sources .*\.sha512$: OK
       - sources .*\.(whl|gz)$: OK
       - wheel .*\.asc$: OK
       - wheel .*\.sha512$: OK
       - wheel .*\.(whl|gz)$: OK
   
   To check installation run:
           docker build -f Dockerfile.pmc -t local/airflow .
           docker local/airflow info
   ```
   
   ```dockerfile
   FROM apache/airflow:1.10.14
   
   # Install backports
   RUN pip install 
'apache-airflow-backport-providers-apache-cassandra==2021.3.17rc1'
   ...
   RUN pip install 'apache-airflow-backport-providers-zendesk==2021.3.17rc1'
   ```
   
   ## Providers
   ```
   ➜ python check_files.py -v 1.0.3rc1 -t providers -p ~/code/airflow_svn
   elasticsearch
       - sources .*\.asc$: OK
       - sources .*\.sha512$: OK
       - sources .*\.(whl|gz)$: OK
       - wheel .*\.asc$: OK
       - wheel .*\.sha512$: OK
       - wheel .*\.(whl|gz)$: OK
   
   To check installation run:
           docker build -f Dockerfile.pmc -t local/airflow .
           docker local/airflow info
   ```
   ```dockerfile
   FROM apache/airflow:latest
   
   # Install providers
   RUN pip install 'apache-airflow-providers-elasticsearch==1.0.3rc1'
   ```
   
   ## Airflow
   ```
   ➜ python check_files.py -v 1.10.15rc1 -t airflow -p ~/code/airflow_svn
   apache_airflow-1.10.15rc1
       - binaries .*\.asc$: OK
       - binaries .*\.sha512$: OK
       - binaries .*\.(whl|gz)$: OK
       - sources .*\.asc$: OK
       - sources .*\.sha512$: OK
       - sources .*\.(whl|gz)$: OK
       - wheel .*\.asc$: OK
       - wheel .*\.sha512$: OK
       - wheel .*\.(whl|gz)$: OK
   
   To check installation run:
           docker build -f Dockerfile.pmc -t local/airflow .
           docker run local/airflow info
   ```
   
   ```dockerfile
   FROM apache/airflow:1.10.14
   
   # Upgrade
   RUN pip install "apache-airflow==1.10.15rc1"
   ```
   
   <!--
   Thank you for contributing! Please make sure that your code changes
   are covered with tests. And in case of new features or big changes
   remember to adjust the documentation.
   
   Feel free to ping committers for the review!
   
   In case of existing issue, reference it using one of the following:
   
   closes: #ISSUE
   related: #ISSUE
   
   How to write a good git commit message:
   http://chris.beams.io/posts/git-commit/
   -->
   
   ---
   **^ Add meaningful description above**
   
   Read the **[Pull Request 
Guidelines](https://github.com/apache/airflow/blob/master/CONTRIBUTING.rst#pull-request-guidelines)**
 for more information.
   In case of fundamental code change, Airflow Improvement Proposal 
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+Proposals))
 is needed.
   In case of a new dependency, check compliance with the [ASF 3rd Party 
License Policy](https://www.apache.org/legal/resolved.html#category-x).
   In case of backwards incompatible changes please leave a note in 
[UPDATING.md](https://github.com/apache/airflow/blob/master/UPDATING.md).
   


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


Reply via email to