canmove, Confirmed users
6,441
edits
ReleaseEngineering/How To/Upload to internal Pypi: Difference between revisions
Jump to navigation
Jump to search
ReleaseEngineering/How To/Upload to internal Pypi (view source)
Revision as of 16:50, 9 October 2025
, 9 Octoberadd note about internal pypi being deprecated
(add note about internal pypi being deprecated) |
|||
| Line 2: | Line 2: | ||
== Overview == | == Overview == | ||
'''!!! internal pypi is deprecated !!!''' | |||
We are looking to [remove this service entirely](https://mozilla-hub.atlassian.net/browse/RELOPS-1835). Packages that Gecko tasks depend on should be vendored into that repository whenever possible. When not possible (eg: binary packages), requirements should be pinned, and the necessary packages fetched from pypi.org instead. | |||
Mozharness no longer uses packages from the PuppetAgain repositories! Instead, it uses http://pypi.pub.build.mozilla.org/pub and http://pypi.pvt.build.mozilla.org/pub, both served from the same directory. | Mozharness no longer uses packages from the PuppetAgain repositories! Instead, it uses http://pypi.pub.build.mozilla.org/pub and http://pypi.pvt.build.mozilla.org/pub, both served from the same directory. | ||