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
This commit is contained in:
parent
e15b9cae77
commit
1ea6374489
@ -4,4 +4,5 @@
|
|||||||
when: zuul_success | bool
|
when: zuul_success | bool
|
||||||
- role: upload-pypi
|
- role: upload-pypi
|
||||||
pypi_path: "{{ zuul.executor.work_root }}/artifacts"
|
pypi_path: "{{ zuul.executor.work_root }}/artifacts"
|
||||||
|
pypi_twine_skip_existing: true
|
||||||
when: zuul_success | bool
|
when: zuul_success | bool
|
||||||
|
Loading…
Reference in New Issue
Block a user