gtristan commented on code in PR #1714:
URL: https://github.com/apache/buildstream/pull/1714#discussion_r945114314
##########
.github/workflows/release.yml:
##########
@@ -32,9 +32,114 @@ jobs:
tar -C doc/build/html -zcf docs.tgz .
+ - uses: actions/upload-artifact@v3
+ with:
+ name: docs
+ path: docs.tgz
+
+ build_sdist:
+ name: "Build Python source distribution tarball"
+ runs-on: ubuntu-20.04
+ steps:
+ - uses: actions/checkout@v3
+ with:
+ fetch-depth: 0
+
+ - name: Build sdist
+ run: pipx run build --sdist
+
+ - uses: actions/upload-artifact@v3
+ with:
+ name: sdist
+ path: dist/*.tar.gz
+
+ build_wheels:
+ name: Build Python wheel packages on ${{ matrix.os }}
+ runs-on: ${{ matrix.os }}
+ strategy:
+ matrix:
+ os: [ubuntu-20.04]
+
+ steps:
+ - uses: actions/checkout@v3
+ with:
+ fetch-depth: 0
+
+ - name: Fetch latest BuildBox release
+ run:
${GITHUB_WORKSPACE}/.github/wheel-helpers/fetch-latest-buildbox-release.sh
+
+ - name: Build wheels
+ run: pipx run cibuildwheel==2.8.1
+
+ - uses: actions/upload-artifact@v3
+ with:
+ name: wheels
+ path: ./wheelhouse/*.whl
+
+ test_wheels:
+ name: Test Python wheel packages on ${{ matrix.os }}
+ needs: [build_wheels]
+ runs-on: ubuntu-20.04
+
+ strategy:
+ matrix:
+ # The names here should map to a valid service defined in
+ # "../compose/ci.docker-compose.yml"
+ test-name:
+ - wheels-manylinux_2_28-cp37
+ - wheels-manylinux_2_28-cp38
+ - wheels-manylinux_2_28-cp39
+ - wheels-manylinux_2_28-cp310
+
+ steps:
+ - uses: actions/checkout@v3
+ with:
+ fetch-depth: 0
+
+ - uses: actions/download-artifact@v3
+ with:
+ name: wheels
+ path: ./wheelhouse
+
+ - name: Run tests with Docker Compose
+ run: |
+ ${GITHUB_WORKSPACE}/.github/run-ci.sh ${{ matrix.test-name }}
+
+ upload_github_release:
+ name: Upload GitHub release assets
+ needs: [build_docs]
Review Comment:
I think that uploading the `docs.tgz` and publishing the wheels should be
contingent on the same steps, we don't want to upload the docs if testing the
releases fail and vice versa.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
