Confirmed users
1,364
edits
ReleaseEngineering/BuildAPI: Difference between revisions
Jump to navigation
Jump to search
added selfserve_agent.py deploy instructions
(added selfserve_agent.py deploy instructions) |
|||
| Line 1: | Line 1: | ||
{{Release Engineering How To|Deploy BuildAPI changes}} | |||
= Overview = | = Overview = | ||
The BuildAPI is a Pylons project used by RelEng to surface information collected from two databases updated through our buildbot masters as they run jobs. | The BuildAPI is a Pylons project used by RelEng to surface information collected from two databases updated through our buildbot masters as they run jobs. | ||
| Line 148: | Line 149: | ||
BuildAPI updates are handled like any other webapp, through pushes. Login to relengwebadm, become root, cd to /data/releng/src/buildapi, and run ./update $rev. | BuildAPI updates are handled like any other webapp, through pushes. Login to relengwebadm, become root, cd to /data/releng/src/buildapi, and run ./update $rev. | ||
=== Selfserve Agent === | |||
Deploying new functionality may require deploying a new version of the <code>scripts/selfserve_agent.py</code> file on build masters. This process is handled by puppet, but orthogonal to buildapi itself. The steps are roughly: | |||
* add a new tag to the buildapi repository (following semantic versioning guidelines, please) | |||
* create a python sdist tarball of that version, and upload to the internal puppetagain python repo. | |||
* update the manifests for the new version in [http://hg.mozilla.org/build/puppet/file/default/modules/selfserve_agent/manifests/install.pp puppet] | |||
* wait for puppet to deploy the new agent. | |||
== Adding branches == | == Adding branches == | ||