This allows us to trigger PyPI uploads from the incoming tag job, rather than
using a crude "this commit matches a tag" workaround.
Details
Details
- Reviewers
douardda - Commits
- rCJSWH47506ba8da32: Add an option to skip running the tests when publishing to PyPI
rCJSWH2f543b2c180c: Make sure the LASTV shell script actually works
rCJSWH1378e56f642f: Rename PYPI parameter to PYPI_HOST and remove PYPI_UPLOAD parameter
rCJSWH881425433344: Split uploading to PyPI into a separate job
tox looks happy; needs some testing on actual jenkins
Diff Detail
Diff Detail
- Repository
- rCJSWH Jenkins jobs
- Lint
Automatic diff as part of commit; lint not applicable. - Unit
Automatic diff as part of commit; unit tests not applicable.
Event Timeline
Comment Actions
This has now been tested through https://jenkins.softwareheritage.org/job/DCORE/job/pypi-upload/
Comment Actions
this looks a very nice improvement. LGTM, let jenkins tells us if I'm right.
jobs/templates/swh-pypi.yaml | ||
---|---|---|
33 | Why not SKIP instead/also? |
jobs/templates/swh-pypi.yaml | ||
---|---|---|
33 | That's a fair point; it would allow us to skip waiting a whole *two* minutes to push an upload *right now* :-) I've also noticed that the FORCE_UPLOAD logic is useless because of PyPI completely preventing you from reusing a filename, even if you delete it before: https://pypi.org/help/#file-name-reuse |