ReleaseEngineering/How To/Update BuildAPI: Difference between revisions
< ReleaseEngineering | How To
Jump to navigation
Jump to search
(Created page with "BuildAPI is composed of a web application plus an agent that runs on a few buildmasters (self-serve agent). So, how do you updat...") |
No edit summary |
||
| Line 1: | Line 1: | ||
[[ReleaseEngineering/Applications/BuildAPI|BuildAPI]] is composed of a web application plus an agent that runs on a few buildmasters (self-serve agent). | [[ReleaseEngineering/Applications/BuildAPI|BuildAPI]] is composed of a web application plus an agent that runs on a few buildmasters (self-serve agent). Also see [[ReleaseEngineering/BuildAPI#Updating_code|ReleaseEngineering/BuildAPI]] | ||
So, how do you update one of those? | So, how do you update one of those? | ||
| Line 5: | Line 5: | ||
= Common = | = Common = | ||
Build a new sdist tarball of BuildAPI, using normal python techniques, and upload it to the puppetagain python repository (/data/python/packages on the distinguished puppetmaster). | Build a new sdist tarball of BuildAPI, using normal python techniques, and upload it to the puppetagain python repository at releng-puppet2.srv.releng.scl3.mozilla.com (/data/python/packages on the distinguished puppetmaster). | ||
** Tarballs can be seen here: http://puppetagain.pub.build.mozilla.org/data/python/packages/ | |||
python setup.py sdist | |||
scp dist/buildapi-0.2.4.tar.gz releng-puppet2.srv.releng.scl3.mozilla.com: | |||
ssh releng-puppet2.srv.releng.scl3.mozilla.com | |||
sudo buildapi-0.2.4.tar.gz /data/python/packages | |||
cd /data/python/packages | |||
sudo chown puppetsync:puppetsync buildapi-0.2.4.tar.gz | |||
sudo chmod 664 buildapi-0.2.4.tar.gz | |||
= Web Application = | = Web Application = | ||
Login to relengwebadm.private.scl3.mozilla.com and become root. Go to /data/releng-stage/src/buildapi (or /releng/ for production) and have a look at README.txt. | * Push new version of BuildAPI to HG | ||
** Edit setup.py to show the updated version (ie version='0.2.3' becomes version='0.2.4') | |||
* Comment out tag_build in setup.cfg - tag_build appends tarball name, among other things | |||
* Login to relengwebadm.private.scl3.mozilla.com and become root. Go to /data/releng-stage/src/buildapi (or /releng/ for production) and have a look at README.txt. Where 0.2.4 is the version you want to install, it boils down to: | |||
./update 0.2.4 | ./update 0.2.4 | ||
= Self-Serve Agent = | = Self-Serve Agent = | ||
Revision as of 22:48, 2 June 2014
BuildAPI is composed of a web application plus an agent that runs on a few buildmasters (self-serve agent). Also see ReleaseEngineering/BuildAPI
So, how do you update one of those?
Common
Build a new sdist tarball of BuildAPI, using normal python techniques, and upload it to the puppetagain python repository at releng-puppet2.srv.releng.scl3.mozilla.com (/data/python/packages on the distinguished puppetmaster).
- Tarballs can be seen here: http://puppetagain.pub.build.mozilla.org/data/python/packages/
python setup.py sdist scp dist/buildapi-0.2.4.tar.gz releng-puppet2.srv.releng.scl3.mozilla.com: ssh releng-puppet2.srv.releng.scl3.mozilla.com sudo buildapi-0.2.4.tar.gz /data/python/packages cd /data/python/packages sudo chown puppetsync:puppetsync buildapi-0.2.4.tar.gz sudo chmod 664 buildapi-0.2.4.tar.gz
Web Application
- Push new version of BuildAPI to HG
- Edit setup.py to show the updated version (ie version='0.2.3' becomes version='0.2.4')
- Comment out tag_build in setup.cfg - tag_build appends tarball name, among other things
- Login to relengwebadm.private.scl3.mozilla.com and become root. Go to /data/releng-stage/src/buildapi (or /releng/ for production) and have a look at README.txt. Where 0.2.4 is the version you want to install, it boils down to:
./update 0.2.4
Self-Serve Agent
Update the version number in puppet, get review, land, and merge to production.