Confirmed users
1,364
edits
ReleaseEngineering/BuildAPI: Difference between revisions
add link to instructions
(added selfserve_agent.py deploy instructions) |
(add link to instructions) |
||
| Line 154: | Line 154: | ||
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: | 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) | * 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. | * create a python sdist tarball of that version, and [[ReleaseEngineering:Buildduty:Other_Duties#Python_packages|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] | * 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. | * wait for puppet to deploy the new agent. | ||