Canmove, confirm
1,394
edits
Changes
Update to describe alembic
Will your change
;require a DB change:If so, you probably want to make that consider carefully whether the DB change beforehand, especially if it's as simple as `relengapi createdb`. If or the code change is incompatible, you'll probably need a change windowto be landed first.
;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 =
scp dist/relengapi-mapper-2.3.4.tar.gz <your user>@relengwebadm.private.scl3.mozilla.com:/tmp
cd /data/releng/src/relengapi
and edit requirements.txt to specify the new version. Now, if you're ready to ship the change live with no DB updates or settings changes: ./update This will upgrade the packages, build the docs, and deploy to the webheads. If you need to do some DB migrations or the like first: ./update -n which will skip the deployment step. Thenupdate the DB schema (assuming the schema upgrade won't break the currently-deployed code from the previous release): ./relengapi.sh alembic relengapi upgrade (or whatever changes you need to make before deploying the code). Finally, deploy the new code with
./update
{{Release Engineering How To|Update RelengAPI}}
