[DEVOPS-234] CI/CD: Build manylinux wheels and upload them to JFrog on every push to an arbitrary branch #606
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Extra changes: When status checks for a workflow are shown due to a push or pull_request event, it will also show status checks for any reusable workflow in it. Only show status check for build-wheels.yml if it's not triggered by a pull request or push event. This prevents status checks for the same build-wheels.yml run from showing twice--one from the workflow that called build-wheels.yml, and another from the build-wheels.yml workflow itself
build-wheels.yml will build wheels on all platforms, but we can optimize this later to only build the manylinux artifacts so we don't waste resources to build the other wheels we don't need
No regression for upload-to-jfrog.yml: https://github.com/aerospike/aerospike-client-python/actions/runs/9177026728
dev-test
branch and a test JFrog repo to check that artifacts are still uploaded to the JFrog PyPI repo properly