-
Notifications
You must be signed in to change notification settings - Fork 16.4k
Don't use author_association for self-hosted vs public runner decision. #14718
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
Don't use author_association for self-hosted vs public runner decision. #14718
Conversation
Using this has two draw-backs for us. 1. MEMBER applies to _anyone in the org_, not just members/commiters to this repo 2. The value of this setting depends upon the user's "visiblity" in the org. I.e. if they hide their membership of the org, the author_association will show up as "CONTRIBUTOR" instead. Both of these combined mean we should instead use an alternative list. Airflow committers is a scret that contains a list of GH user ids, such as `["ashb", "..."]` etc.
|
Hmmm. |
|
Damn, It seems you can't reference secrets nor env in the |
|
Trying to include a hard-coded list in the ci.yaml (it's verifired/checked again on the runner so is "safe") fails too:
Damn, not sure this is actually possible :/ |
|
|
|
The Workflow run is cancelling this PR. Building image for the PR has been cancelled |
|
Down to at least one hard-coded list now. |
|
There, working, and not too horrible/duplictative. I would have liked to be able to use secrets, but sadly not possible. |
|
Jobs after the first are running on self-hosted runners, don't need to wait on tests. |
|
|
||
| env: | ||
|
|
||
| AIRFLOW_COMMITERS: ${{ secrets.AIRFLOW_COMMITERS }} |
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.
I guess we can remove this one? That turned out to be not working for forked PRs I believe?
The change apache#14718 by mistake left the 'self-hosted" runs-on in case of push or schedule. This caused failures on non-apache repositories.
The change #14718 by mistake left the 'self-hosted" runs-on in case of push or schedule. This caused failures on non-apache repositories.
…n. (#14718) Using this has two draw-backs for us. 1. MEMBER applies to _anyone in the org_, not just members/commiters to this repo 2. The value of this setting depends upon the user's "visiblity" in the org. I.e. if they hide their membership of the org, the author_association will show up as "CONTRIBUTOR" instead. Both of these combined mean we should instead use an alternative list. We can't use a secret as the `secrets.` context is not available in the runs-on stanza, so we have to have a hard-coded list in the workflow file :( This is as secure as the runner still checks the author against it's own list. (cherry picked from commit 4213487)
…n. (#14718) Using this has two draw-backs for us. 1. MEMBER applies to _anyone in the org_, not just members/commiters to this repo 2. The value of this setting depends upon the user's "visiblity" in the org. I.e. if they hide their membership of the org, the author_association will show up as "CONTRIBUTOR" instead. Both of these combined mean we should instead use an alternative list. We can't use a secret as the `secrets.` context is not available in the runs-on stanza, so we have to have a hard-coded list in the workflow file :( This is as secure as the runner still checks the author against it's own list. (cherry picked from commit 4213487)
Using this has two draw-backs for us.
Both of these combined mean we should instead use an alternative list. Airflow committers is a scret that contains a list of GH user ids, such as
["ashb", "..."]etc.