[BEAM-9388] Consider using github actions for building python wheels and more (aka. Transition from Travis)

• Type: Wish
• Status: Resolved
• Priority: P2
• Resolution: Fixed
• Fix Version/s: Missing
• Component/s: build-system, sdk-py-core
• Labels: stale-P2
• Assignee: Tobiasz Kedzierski
• Reporter: Ahmet Altay
• Created: 26/Feb/20 18:03
• Updated: 13/Jan/22 21:52
• Resolved: 15/May/21 18:01

Description

Context on the mailing list: https://lists.apache.org/thread.html/r4a7d34e64a34e9fe589d06aec74d9b464d252c516fe96c35b2d6c9ae%40%3Cdev.beam.apache.org%3E

github actions instead of travis to for building python wheels during releases. This will have the following advantages:

• We will eliminate one repo. (If you don't know, we have https://github.com/apache/beam-wheels for the sole purpose of building wheels file.)
• Workflow will be stored in the same repo. This will prevent bit rot that is only discovered at release times. (happened a few times, although usually easy to fix.)
• github actions supports ubuntu, mac, windows environments. We could try to build wheels for windows as well. (Travis also supports the same environments but we only use linux and mac environments. Maybe there are other blockers for building wheels for Windows.)
• We could do more, like daily python builds.

Issue Links

• is related to: BEAM-10599 Add documentation about CI on GitHub Action

Sub-Tasks

• Build python wheels on GitHub Actions for Linux/MacOS: Resolved
• Build python wheels on GitHub Actions for Windows: Resolved
• Use GitHub Actions in release process (python): Resolved
• Periodic clear of GCS wheels staging bucket: Resolved
• Cancel queued/running GitHub Action builds on second push to PR: Resolved
• Add checksum for Python source distribution and wheels: Resolved