-
Notifications
You must be signed in to change notification settings - Fork 14.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
For v1-10-test PRs and pushes, use target branch scripts for images #12339
For v1-10-test PRs and pushes, use target branch scripts for images #12339
Conversation
The PR needs to run all tests because it modifies core of Airflow! Please rebase it to latest master or ask committer to re-run it! |
Testing it here: Direct push to master: https://github.com/potiuk/airflow/actions/runs/361589802
PR: from a fork to master: https://github.com/potiuk/airflow/actions/runs/361596665 higrys -> potiuk
Direct push to v1-10-test (stable will work the same): https://github.com/potiuk/airflow/actions/runs/361597050
PR from a fork to v1-10-test (stable will work the same): https://github.com/potiuk/airflow/actions/runs/361597777 higrys -> potiuk
This should cause much more predictable builds for "non-master-branch" PRs and direct pushes (scripts from the target branch are used to build images in "workflow_run" Build Image runs ) . |
040222b
to
229a951
Compare
One small update @kaxil -> i noticed that the Job name overriding the scripts still mentioned master, now it will tell exactly from which branch the scripts are used. |
if: steps.defaults.outputs.proceed == 'true' | ||
- name: "Setup python" | ||
uses: actions/setup-python@v2 | ||
with: | ||
python-version: ${{ needs.build-info.outputs.defaultPythonVersion }} | ||
if: steps.defaults.outputs.proceed == 'true' | ||
- name: "Override 'scripts/ci' with the ${{ github.ref }} version so that the PR cannot override it." | ||
- name: | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here we tell exactly which version of the scripts is used to build the images @kaxil
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
And checkout still has "master" (just in the job name) . |
eeh yeah, can we update that |
absolutely! |
229a951
to
86eefec
Compare
Previously, always master scripts were used to build images for workflow_run, because workflow_run always runs from master branch. However that causes some surprising effects becuase the sripts from master had to support both master and 1.10. This change utilises a new feature in the "get-workflow-origin" action - to get the target branch of PR and uses ci scripts from that target branch. This is perfectly secure, because both v1-10-test, v1-10-stable and future 2-0 branches can only be updated by committers, either by direct push or by merge.
86eefec
to
cd0d1b2
Compare
…12339) Previously, always master scripts were used to build images for workflow_run, because workflow_run always runs from master branch. However that causes some surprising effects becuase the sripts from master had to support both master and 1.10. This change utilises a new feature in the "get-workflow-origin" action - to get the target branch of PR and uses ci scripts from that target branch. This is perfectly secure, because both v1-10-test, v1-10-stable and future 2-0 branches can only be updated by committers, either by direct push or by merge. (cherry picked from commit 7c4fe19)
…12339) Previously, always master scripts were used to build images for workflow_run, because workflow_run always runs from master branch. However that causes some surprising effects becuase the sripts from master had to support both master and 1.10. This change utilises a new feature in the "get-workflow-origin" action - to get the target branch of PR and uses ci scripts from that target branch. This is perfectly secure, because both v1-10-test, v1-10-stable and future 2-0 branches can only be updated by committers, either by direct push or by merge. (cherry picked from commit 7c4fe19)
…12339) Previously, always master scripts were used to build images for workflow_run, because workflow_run always runs from master branch. However that causes some surprising effects becuase the sripts from master had to support both master and 1.10. This change utilises a new feature in the "get-workflow-origin" action - to get the target branch of PR and uses ci scripts from that target branch. This is perfectly secure, because both v1-10-test, v1-10-stable and future 2-0 branches can only be updated by committers, either by direct push or by merge. (cherry picked from commit 7c4fe19)
…12339) Previously, always master scripts were used to build images for workflow_run, because workflow_run always runs from master branch. However that causes some surprising effects becuase the sripts from master had to support both master and 1.10. This change utilises a new feature in the "get-workflow-origin" action - to get the target branch of PR and uses ci scripts from that target branch. This is perfectly secure, because both v1-10-test, v1-10-stable and future 2-0 branches can only be updated by committers, either by direct push or by merge. (cherry picked from commit 7c4fe19)
…pache#12339) Previously, always master scripts were used to build images for workflow_run, because workflow_run always runs from master branch. However that causes some surprising effects becuase the sripts from master had to support both master and 1.10. This change utilises a new feature in the "get-workflow-origin" action - to get the target branch of PR and uses ci scripts from that target branch. This is perfectly secure, because both v1-10-test, v1-10-stable and future 2-0 branches can only be updated by committers, either by direct push or by merge. (cherry picked from commit 7c4fe19)
Previously, always master scripts were used to build images
for workflow_run, because workflow_run always runs from master
branch. However that causes some surprising effects becuase the
sripts from master had to support both master and 1.10.
This change utilises a new feature in the "get-workflow-origin"
action - to get the target branch of PR and uses ci scripts from that
target branch.
This is perfectly secure, because both v1-10-test, v1-10-stable
and future 2-0 branches can only be updated by committers,
either by direct push or by merge.
^ 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.