Update CI service names referenced in buildbots.rst #739
Conversation
|
Hello, and thanks for your contribution! I'm a bot set up to make sure that the project can legally accept this contribution by verifying everyone involved has signed the PSF contributor agreement (CLA). CLA MissingOur records indicate the following people have not signed the CLA: For legal reasons we need all the people listed to sign the CLA before we can look at your contribution. Please follow the steps outlined in the CPython devguide to rectify this issue. If you have recently signed the CLA, please wait at least one business day You can check yourself to see if the CLA has been received. Thanks again for the contribution, we look forward to reviewing it! |
the-knights-who-say-ni
added
CLA not signed
CLA signed
and removed
CLA not signed
labels
|
The CLA bit is updated. I'm trying to understand what the current state of CI services used is and when they are run -- I've seen issues that about switching to GitHub Actions (running for PRs+commits) from Travis (only running for commits), but it's not clear what the state of the transition is, and I'm not seeing anything about how the jobs on Azure Pipelines fit in. Are there any pointers for where to look for additional documentation on the non-buildbot CI setup and what work is in progress/needs to get done? It would be nice to add more information on the CI setup to the devguide and figure out what work needs to get done, but so far with the scattered issues I've come across I feel like I need a guide to get me oriented on what is currently up to date. |
| When working on a platform-specific issue, you may want to test your changes on | ||
| the buildbot fleet rather than just on Travis and AppVeyor. To do so, you can | ||
| the buildbot fleet rather than just on GitHub Actions and Azure Pipelines. To do so, you can |
There was a problem hiding this comment.
This seems to be the only place in the entire devguide that mentions CI services other than the Python buildbot. Maybe it would be better to remove the outdated line, and later on add more detail on the non-buildbot CI setup?
Looks good, GHA and AP are now used in place of Travis and AppVeyor as the standard CI.
Minor fix changing the CI service names referenced in buildbots.rst from AppVeyor and Travis which appear to have been replaced with GitHub Actions and Azure Pipelines for running tests on PRs.