canmove, Confirmed users
6,441
edits
ReleaseEngineering/Buildbot Best Practices: Difference between revisions
Jump to navigation
Jump to search
ReleaseEngineering/Buildbot Best Practices (view source)
Revision as of 15:18, 11 March 2009
, 11 March 2009no edit summary
(New page: <h2>WIP</h2> We've gotten to the point of having many different masters, and more complex masters. It's becoming more and more important to have consistent setup in terms of where configu...) |
No edit summary |
||
| Line 1: | Line 1: | ||
<h2>WIP</h2> | <h2>WIP</h2> | ||
We've gotten to the point of having many different masters, and more complex masters. It's becoming more and more important to have consistent setup in terms of where configuration files are stored, where supporting code is stored, and other such details. This document is a rulebook and guideline for how to | We've gotten to the point of having many different masters, and more complex masters. It's becoming more and more important to have consistent setup in terms of where configuration files are stored, where supporting code is stored, and other such details. This document is a rulebook and guideline for how to maintain these machines and instances. | ||
== Repositories == | |||
* [http://hg.mozilla.org/build/buildbot-configs/ buildbot-configs] - This repository contains Buildbot master.cfg and mozconfig files for most of our Buildbot instances. | |||
* [http://hg.mozilla.org/build/buildbotcustom/ buildbotcustom] - This repository contains custom steps, factories, and other Mozilla specific Buildbot code required by our Buildbot masters. | |||
* [http://hg.mozilla.org/build/buildbot/ buildbot] - This repository is an import of upstream Buildbot code, plus some patches that we require. | |||