ReleaseEngineering/How To/Upload to internal Pypi: Difference between revisions
< ReleaseEngineering | How To
Jump to navigation
Jump to search
No edit summary |
(added link to the example bug) |
||
| Line 1: | Line 1: | ||
=Overview= | = Overview = | ||
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. | ||
=Steps= | = Steps = | ||
* In order to upload to internal Pypi a package you simply need to run the script bellow : | * In order to upload to internal Pypi a package you simply need to run the script bellow : | ||
| Line 11: | Line 11: | ||
= See also = | |||
* [https://bugzilla.mozilla.org/show_bug.cgi?id=1286278 bug 1286278] | |||
Revision as of 10:17, 5 December 2017
Overview
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.
Steps
- In order to upload to internal Pypi a package you simply need to run the script bellow :
https://hg.mozilla.org/build/braindump/file/default/utils/publish_package_our_pypi.sh
The script will practically copy the file to relengwebadmin and move it where the files are located for pypi internal (/mnt/netapp/relengwebadmin/pypi/pub) then will change the rights and upload the file to http://pypi.pub.build.mozilla.org/pub.