Confirmed users
1,364
edits
ReleaseEngineering/BuildAPI: Difference between revisions
Jump to navigation
Jump to search
yet more steps
(more steps for tarball production) |
(yet more steps) |
||
| Line 153: | Line 153: | ||
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: | ||
* | |||
* create a python sdist tarball of that version | * bump the version of the buildapi repository in "<code>setup.py</code>" and commit (following semantic versioning guidelines, please) | ||
* add a new tag to the buildapi repository for that version, commit & push | |||
* create a python sdist tarball of that version: | |||
** make sure you have a clean checkout | ** make sure you have a clean checkout | ||
** locally modify (but do not commit) <code>setup.cfg</code> and comment out "<code>tag_build</code>" | ** locally modify (but do not commit) <code>setup.cfg</code> and comment out "<code>tag_build</code>" | ||
** run "python setup.py "<code>sdist</code>" | ** run "python setup.py "<code>sdist</code>" | ||
** updload the file from "<code>dist/</code>" | ** updload the file from "<code>dist/</code>" | ||
* [[ReleaseEngineering/How_To/Add_a_Python_Package_to_PuppetAgain|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. | ||