-
Notifications
You must be signed in to change notification settings - Fork 787
[CI] Let sycl-devops-pr/** branches trigger pre/post-commit #10002
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
Conversation
In #9950 I envisioned a setup when there will be a dedicated devops pre-commit task that would create fake branch/PR in the repository to verify changes affecting CI. I later realized that we can just push the source branch for such a PR directly to origin and use that for testing. As such, rename which branch is allowed to trigger post-commit and allow the same for pre-commit.
Tested I've cancelled both of the runs after initial/first task finished because the trigger itself is being changed in this PR. |
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 like this idea!
It was originally added in #10002, back when we used `pull_request_target` for pre-commit trigger. Now that `pull_request` is used it isn't (as) necessary. I'm also adding a `workflow_dispatch` trigger for the post-commit job for cases when somebody wants to test extensive non-CI changes with post-commit before the merge. I think that will work but it's impossible to verify before merging this due to how GHA work. This will address the following usage scenario: * Push CI-related changes to `sycl-devops-pr` (possibly several iterations) * Result are ok, open a PR from that branch - extra post-commit task is spawned for the commit that has been tested already (this duplication will remain, unfortunately) * Address review feedback with a new upload - two post-commit jobs are automatically launched (after this PR, no manual dispatch would happen here, leaving only automatic pre-commit testing of the post-commit workflow)
It was originally added in #10002, back when we used `pull_request_target` for pre-commit trigger. Now that `pull_request` is used it isn't (as) necessary. I'm also adding a `workflow_dispatch` trigger for the post-commit job for cases when somebody wants to test extensive non-CI changes with post-commit before the merge. I think that will work but it's impossible to verify before merging this due to how GHA work. This will address the following usage scenario: * Push CI-related changes to `sycl-devops-pr` (possibly several iterations) * Result are ok, open a PR from that branch - extra post-commit task is spawned for the commit that has been tested already (this duplication will remain, unfortunately) * Address review feedback with a new upload - two post-commit jobs are automatically launched (after this PR, no manual dispatch would happen here, leaving only automatic pre-commit testing of the post-commit workflow)
In #9950 I envisioned a setup when there will be a dedicated devops pre-commit task that would create fake branch/PR in the repository to verify changes affecting CI. I later realized that we can just push the source branch for such a PR directly to origin and use that for testing.
As such, rename which branch is allowed to trigger post-commit and allow the same for pre-commit. Future changes are expected to be done like this:
sycl-devops-pr/<name>
in intel/llvm repo, it willrun post-commit testing.
sycl-devops-pr/<name>
, that will run pre-commit testing.