Page MenuHomeSoftware Heritage

Split uploading to PyPI into a separate job
ClosedPublic

Authored by olasd on Nov 26 2018, 5:25 PM.

Details

Summary

This allows us to trigger PyPI uploads from the incoming tag job, rather than
using a crude "this commit matches a tag" workaround.

Test Plan

tox looks happy; needs some testing on actual jenkins

Diff Detail

Repository
rCJSWH Jenkins jobs
Branch
master
Lint
No Linters Available
Unit
No Unit Test Coverage
Build Status
Buildable 2611
Build 3244: arc lint + arc unit

Event Timeline

  • Rename PYPI parameter to PYPI_HOST and remove PYPI_UPLOAD parameter
  • Make sure the LASTV shell script actually works

Feedback from tests on the live jenkins instance

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?

This revision is now accepted and ready to land.Nov 27 2018, 12:00 PM
olasd added inline comments.
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

olasd marked an inline comment as done.
  • Add an option to skip running the tests when publishing to PyPI
This revision was automatically updated to reflect the committed changes.