potiuk opened a new pull request #13772:
URL: https://github.com/apache/airflow/pull/13772


   We've introduced chmod a+x for installation scripts in Dockerfiles.
   but this turned out to be a bad idea. This was to accomodate
   building on Azure Deveops which has filesystem that does not
   keep executable bit. But the side-effect of it that the
   layer of the script is invalidated when the permission is changed
   to +x on linux. The problem is that the script has locally (on
   checkout) different permissions depending on umask setting.
   
   Therefore changing permissions for the image to +a is not best.
   
   Instead we are running the scripts with bash directly, which does
   not require changing of executable bit.
   
   <!--
   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