Hello, Tony, Yes, just follow the [2] to tag a release. Maybe the issue is the version naming, using "v2.0.0 " is the problem, I guess, only number no character is allowed.
Thank you, will try again. Best Regards Chaoyi Huang ( Joe Huang ) -----Original Message----- From: Tony Breeds [mailto:[email protected]] Sent: Friday, June 17, 2016 10:39 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Infra] publish-to-pypi not working in Tricircle stable/mitaka branch On Fri, Jun 17, 2016 at 01:15:13AM +0000, joehuang wrote: > Hello, > > The publish-to-pypi job is configured for Tricircle[1], and already > gave "openstackci" the role to "Owner"[3][2]. > > After push a new tag v2.0.1 in stable/mitaka branch of : > https://github.com/openstack/tricircle, the tagging is successfully > applied to the repository, but the publish-to-pypi job did not work, > and no package was published. I'm *far* form an expert but I think that the release pipeline only triggers on tags that match this pattern: ^refs/tags/[0-9]+(\.[0-9]+)*$ from [1] Also I want to be sure that you tagged the repo in the openstck infrastructure (as opposed to guthub) as outlined in [2] Yours Tony. [1] http://git.openstack.org/cgit/openstack-infra/project-config/tree/zuul/layout.yaml#n128 [2] http://docs.openstack.org/infra/manual/drivers.html#tagging-a-release __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
