Confirmed users
142
edits
ReleaseEngineering/How To/Update RelengAPI: Difference between revisions
Jump to navigation
Jump to search
ReleaseEngineering/How To/Update RelengAPI (view source)
Revision as of 14:39, 20 May 2014
, 20 May 2014→Shipping It
(Created page with "RelengAPI is composed of a bunch of different Python distributions. You can see the current versions at https://api.pub.build.mo...") |
|||
| Line 18: | Line 18: | ||
Upload the resulting tarball (in `dist/`) to relengapi: | Upload the resulting tarball (in `dist/`) to relengapi: | ||
scp dist/relengapi-mapper-2.3.4 relengwebadm.private.scl3.mozilla.com:/tmp | scp dist/relengapi-mapper-2.3.4.tar.gz <your user>@relengwebadm.private.scl3.mozilla.com:/tmp | ||
and put it in place on relengwebadm as root | and put it in place on relengwebadm as root | ||
mv /tmp/relengapi-mapper-2.3.4 /mnt/netapp/relengweb/pypi/pub | mv /tmp/relengapi-mapper-2.3.4.tar.gz /mnt/netapp/relengweb/pypi/pub | ||
Please note the files will still be owned by your user, so you should make it universally readable: | |||
chmod a+r /mnt/netapp/relengweb/pypi/pub/relengapi-mapper-2.3.4.tar.gz | |||
Also on relengwebadm, cd to the source directory for staging or production | Also on relengwebadm, cd to the source directory for staging or production | ||