Jeremy Stanley 1ea6374489 Skip existing remote artifacts during PyPI upload ... In order to be able to safely re-enqueue tags which previously failed release jobs after successfully uploading at least some artifacts to PyPI, instruct twine to treat "file already exists" responses as benign and ignore them, proceeding to upload any others which aren't yet there. Depends-On: https://review.opendev.org/864004 Change-Id: Iab38df6386ce5219a52787fda5e64a8faab23a06		2022-11-08 15:41:47 +00:00
..
install-guide.yaml	Migrate to upload-afs-roots role	2020-02-03 14:16:39 +11:00
openstack-afs.yaml	Migrate to upload-afs-roots role	2020-02-03 14:16:39 +11:00
openstack-artifacts.yaml	linter: add name to blocks	2022-07-28 12:03:23 +10:00
publications-index.yaml	Use playbooks/publish/openstack-afs everywhere	2018-02-18 08:46:49 +01:00
publications.yaml	Use playbooks/publish/openstack-afs everywhere	2018-02-18 08:46:49 +01:00
puppetforge.yaml	Rework to use new upload-forge module	2019-02-11 11:44:34 +00:00
pypi.yaml	Skip existing remote artifacts during PyPI upload	2022-11-08 15:41:47 +00:00
releasenotes.yaml	Add root_marker_dir for releasenotes publish	2020-05-28 10:32:58 +02:00
releases-afs.yaml	Add AFS publish job for releases repo	2020-02-20 18:04:14 +01:00
starlingx-afs.yaml	Migrate to upload-afs-roots role	2020-02-03 14:16:39 +11:00
trigger-rtd.yaml	trigger-rtd: fix role syntax	2022-07-28 12:01:50 +10:00
wheel-mirror.yaml	linter: use spaces between filters in jinja	2022-07-28 12:03:59 +10:00