VirusTotal / yara-python

The Python interface for YARA
http://virustotal.github.io/yara/
Apache License 2.0
637 stars 178 forks source link

ci: add a github workflow to build and publish linux wheels #250

Closed florianvazelle closed 5 months ago

florianvazelle commented 5 months ago

Hi :wave:

I submit a PR to build linux wheels in CI, related to my issue https://github.com/VirusTotal/yara-python/issues/249.

I use pypa/cibuildwheel to build linux wheels on multiple versions of Python.

This workflow :

  1. Generate a zip file as artifacts, that contains several wheels:

    yara_python-4.4.0-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
    yara_python-4.4.0-cp310-cp310-manylinux_2_5_i686.manylinux1_i686.manylinux_2_17_i686.manylinux2014_i686.whl
    yara_python-4.4.0-cp310-cp310-musllinux_1_1_i686.whl
    yara_python-4.4.0-cp310-cp310-musllinux_1_1_x86_64.whl
    yara_python-4.4.0-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
    yara_python-4.4.0-cp311-cp311-manylinux_2_5_i686.manylinux1_i686.manylinux_2_17_i686.manylinux2014_i686.whl
    yara_python-4.4.0-cp311-cp311-musllinux_1_1_i686.whl
    yara_python-4.4.0-cp311-cp311-musllinux_1_1_x86_64.whl
    yara_python-4.4.0-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
    yara_python-4.4.0-cp312-cp312-manylinux_2_5_i686.manylinux1_i686.manylinux_2_17_i686.manylinux2014_i686.whl
    yara_python-4.4.0-cp312-cp312-musllinux_1_1_i686.whl
    yara_python-4.4.0-cp312-cp312-musllinux_1_1_x86_64.whl
    yara_python-4.4.0-cp36-cp36m-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
    yara_python-4.4.0-cp36-cp36m-manylinux_2_5_i686.manylinux1_i686.manylinux_2_17_i686.manylinux2014_i686.whl
    yara_python-4.4.0-cp36-cp36m-musllinux_1_1_i686.whl
    yara_python-4.4.0-cp36-cp36m-musllinux_1_1_x86_64.whl
    yara_python-4.4.0-cp37-cp37m-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
    yara_python-4.4.0-cp37-cp37m-manylinux_2_5_i686.manylinux1_i686.manylinux_2_17_i686.manylinux2014_i686.whl
    yara_python-4.4.0-cp37-cp37m-musllinux_1_1_i686.whl
    yara_python-4.4.0-cp37-cp37m-musllinux_1_1_x86_64.whl
    yara_python-4.4.0-cp38-cp38-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
    yara_python-4.4.0-cp38-cp38-manylinux_2_5_i686.manylinux1_i686.manylinux_2_17_i686.manylinux2014_i686.whl
    yara_python-4.4.0-cp38-cp38-musllinux_1_1_i686.whl
    yara_python-4.4.0-cp38-cp38-musllinux_1_1_x86_64.whl
    yara_python-4.4.0-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
    yara_python-4.4.0-cp39-cp39-manylinux_2_5_i686.manylinux1_i686.manylinux_2_17_i686.manylinux2014_i686.whl
    yara_python-4.4.0-cp39-cp39-musllinux_1_1_i686.whl
    yara_python-4.4.0-cp39-cp39-musllinux_1_1_x86_64.whl
    yara_python-4.4.0-pp310-pypy310_pp73-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
    yara_python-4.4.0-pp310-pypy310_pp73-manylinux_2_5_i686.manylinux1_i686.manylinux_2_17_i686.manylinux2014_i686.whl
    yara_python-4.4.0-pp37-pypy37_pp73-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
    yara_python-4.4.0-pp37-pypy37_pp73-manylinux_2_5_i686.manylinux1_i686.manylinux_2_17_i686.manylinux2014_i686.whl
    yara_python-4.4.0-pp38-pypy38_pp73-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
    yara_python-4.4.0-pp38-pypy38_pp73-manylinux_2_5_i686.manylinux1_i686.manylinux_2_17_i686.manylinux2014_i686.whl
    yara_python-4.4.0-pp39-pypy39_pp73-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
    yara_python-4.4.0-pp39-pypy39_pp73-manylinux_2_5_i686.manylinux1_i686.manylinux_2_17_i686.manylinux2014_i686.whl
  2. Automatically publish wheels to PyPI, on pushed tag, but required some configuration on the PyPI repo, to configure the workflow as a trusted publisher (see configuring-trusted-publishing).

google-cla[bot] commented 5 months ago

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.