-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
CI: add GitHub actions for macos (push based) #29032
Conversation
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 think it's possible to reuse workflows that are almost the same, calling them with input parameters from a caller workflow. See https://docs.github.com/en/actions/learn-github-actions/reusing-workflows
Other than that, LGTM
What's the overall strategy? Migrate everything on GithubActions or only MacOS builds? |
Status updateI just reenabled this particular PR to be able to evaluate this approach in addition to the Orka one. It will run by default for every push in the 7., 8. and master branches |
I thought the backport was not needed as long as the default branch contained the github actions with the OTOH, interestingly, the |
(cherry picked from commit 6c40884)
(cherry picked from commit 6c40884)
What does this PR do?
Add the minimal GitHub actions for MacOS on a push based.
Why is it important?
Infra asked to evaluate this and the cost.
Issues
Notifies #28906 that will provide the integration with Jenkins and other better user experience