Fix file permissions in all build commands #22656
Conversation
Moves group permission cleanup to build command in new Breeze2. Seems that we should fix group permissions in all build commands. That will shave extra few minutes on most builds where they modify sources. Also the output from the build will be a bit cleaner by removing come of the console outputs.
potiuk
force-pushed
the
improve-output-of-commands
branch
from
f14462d to
b83028c
Compare
|
@dstandish - few more minutes saved in some cases with this one :) |
|
cc: @Bowrna @edithturn - seems that I am ready to start replacing the old Breeze code with this one :). Watch this space. |
|
2 minutes per build saved with it :) |
|
@potiuk this is impressive 💪🏼 , If I want to test this, should I install Breeze, right? |
Yep. |
what more do you need @potiuk, could I help with the test? |
|
Naaa. I tested it :) |
github-actions
bot
added
the
okay to merge
|
The PR is likely ready to be merged. No tests are needed as no important environment files, nor python files were modified by it. However, committers might decide that full test matrix is needed and add the 'full tests needed' label. Then you should rebase it to the latest main or amend the last commit of the PR, and push it with --force-with-lease. |
3 participants
Moves group permission cleanup to build command in new Breeze2.
Seems that we should fix group permissions in all build commands.
That will shave extra few minutes on most builds where they
modify sources. Also the output from the build will be a bit
cleaner by removing come of the console outputs.
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code change, Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in UPDATING.md.