Open Stack

On 09/10/2018 09:39 AM, Tony Breeds wrote:
> Julien, Do you mind me arranging for at least the following versions to
> be published to pypi?

For this particular case, I think our best approach is to have an
admin manually upload the tar & wheels from tarballs.openstack.org to
pypi.  All other options seem to be sub-optimal:

  - if we re-ran the release pipeline, I *think* it would all be
    idempotent and the publishing would happen, but there would be
    confusing duplicate release emails sent.

  - we could make a special "only-publish" template that avoids
    notification jobs; switch ceilometer to this, re-run the releases,
    then switch back.  urgh, especially if something goes wrong.

  - ceilometer could make "no-op" releases on each branch to trigger a
    fresh release & publish; but releases that essentially do nothing
    are I imagine an annoyance for users and distributors who track
    stable branches.

It would look like

   https://test.pypi.org/project/ceilometer/

The pypi hashes will all line up with the .asc files we publish, so we
know there's no funny business going on.

Thanks,

-i