-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
WIP: All the CI in GitHub actions (DO NOT MERGE) #29715
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
WIP: All the CI in GitHub actions (DO NOT MERGE) #29715
Conversation
…h just once per job
@datapythonista anything i/others can do to help with this? |
So far I'm mainly experimenting, to see challenges and what can be done. There are several builds that are working now, but I'd probably wait for now, before moving anything. I'd probably start by the web+docs build, and the ones in travis, and those are the ones that are failing (besides the windows ones). What's your idea? If you'd like to see things in GitHub actions soon, we can discuss and see how can split this already. Is there anything that you think we should prioritize? |
I don't have any ideas, no, just was going through PRs and seeing where I might be useful |
…nd removing action to clean up PR docs
Closing this, was just for testing. Will propose new builds to GitHub actions incrementally. |
Many things are incomplete or broken here, but opening this so people can see the progress.
This needs to be discussed, and if we move forward splitted in many PRs, before it can be merged.
This adds all our current builds to GitHub actions, with two new features:
Finalize
job is triggered when all the others are finished, that should summarize the errors in a GitHub comment (WIP)Some things that are broken:
Finalize
job is WIP, and not sure if even triggeredI'll probably work on #29685 before adding any test build to actions. I think we can do much better in terms of simplicity and coverage with the creation of the matrix (which builds we run, and what's tested in each).