Make releases from CI

[tilgovi]

I was just reading about cibuildwheel¹. Do we have any interest in automating releases like this?

[benoitc]

I'm all for automating the release if we can. This looks good for me. Do you think we can do it only when a version is tagged?

[tilgovi]

Definitely we can make it happen only when tagged.

[tilgovi]

The example in the README contains this code:

  # if the release was tagged, upload them to PyPI
  - |
    if [[ $TRAVIS_TAG ]]; then
      python -m pip install twine
      python -m twine upload wheelhouse/*.whl
    fi

[benoitc]

oh I didn't see it... that's good! I would be more than happy to automate such thing. So no more error and such

[tilgovi]

I'll work on it.

[jamadden]

The zopefoundation repos that I work on recently updated the way they do this. They generate multiple binary wheels for Windows and Linux so the configuration is more complex than what is needed here & now, but it's been iterated on several times and I think it's a good example of using Docker/Linux and macOS. There may be some usable parts there.

Here's one that builds and uploads binaries on Travis. The sibling appveyor.yml is for Windows.

[benoitc]

while we are here we should also test some scenarios on different platforms (signals, reload, reexec..) so we can make sure the code is cross platform. I'm thinking we could create github project for that and collect from there the tickets. Thoughts?

[benoitc]

no activity since awhile. closing feel free to create a new ticket if needed.

[pajod]

There is activity in the form of a (in its current state, just going though the motions, not actually releasing) github workflow suggested here in #3134 - see https://github.com/benoitc/gunicorn/pull/3134/files#diff-87db21a973eed4fef5f32b267aa60fcee5cbdf03c67fafdc2a9b553bb0b15f34R32-R38