Canmove, confirm
1,394
edits
Changes
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..."
[[ReleaseEngineering/Applications/RelengAPI|RelengAPI]] is composed of a bunch of different Python distributions. You can see the current versions at https://api.pub.build.mozilla.org/versions.
So, how do you update one of those?
= Cautions =
Will your change
;require a DB change:If so, you probably want to make that change beforehand, especially if it's as simple as `relengapi createdb`. If the change is incompatible, you'll probably need a change window.
;make an incompatible API change:If so, you should endeavor to make it non-incompatible, and otherwise announce the change to any users beforehand.
= Shipping It =
In whatever distribution you're working on, bump the version number (in `setup.py`), git tag it with the distribution name, `-`, version, e.g., `relengapi-mapper-2.3.4`, and push.
Build an sdist tarball:
python setup.py sdist
Upload the resulting tarball (in `dist/`) to relengapi:
scp dist/relengapi-mapper-2.3.4 relengwebadm.private.scl3.mozilla.com:/tmp
and put it in place on relengwebadm as root
mv /tmp/relengapi-mapper-2.3.4 /mnt/netapp/relengweb/pypi/pub
Also on relengwebadm, cd to the source directory for staging or production
cd /data/releng-stage/src/relengapi
cd /data/releng/src/relengapi
and edit requirements.txt to specify the new version. Then
./update
will upgrade the packages, build the docs, and deploy to the webheads.
{{Release Engineering How To|Update RelengAPI}}
So, how do you update one of those?
= Cautions =
Will your change
;require a DB change:If so, you probably want to make that change beforehand, especially if it's as simple as `relengapi createdb`. If the change is incompatible, you'll probably need a change window.
;make an incompatible API change:If so, you should endeavor to make it non-incompatible, and otherwise announce the change to any users beforehand.
= Shipping It =
In whatever distribution you're working on, bump the version number (in `setup.py`), git tag it with the distribution name, `-`, version, e.g., `relengapi-mapper-2.3.4`, and push.
Build an sdist tarball:
python setup.py sdist
Upload the resulting tarball (in `dist/`) to relengapi:
scp dist/relengapi-mapper-2.3.4 relengwebadm.private.scl3.mozilla.com:/tmp
and put it in place on relengwebadm as root
mv /tmp/relengapi-mapper-2.3.4 /mnt/netapp/relengweb/pypi/pub
Also on relengwebadm, cd to the source directory for staging or production
cd /data/releng-stage/src/relengapi
cd /data/releng/src/relengapi
and edit requirements.txt to specify the new version. Then
./update
will upgrade the packages, build the docs, and deploy to the webheads.
{{Release Engineering How To|Update RelengAPI}}
