947
edits
Auto-tools/Projects/MozmillBuildbot: Difference between revisions
Jump to navigation
Jump to search
m
→Long-term Recommendations: addtl instructions
m (→Long-term Recommendations: note restart script) |
m (→Long-term Recommendations: addtl instructions) |
||
| Line 57: | Line 57: | ||
However, for the case of TTW force builds, <tt>build.source.changes</tt> is an empty tuple, so the step fails with an exception. In general, if <tt>build.source.changes</tt> is empty, a URL should be constructed from the platform and other variables appropriate to the build | However, for the case of TTW force builds, <tt>build.source.changes</tt> is an empty tuple, so the step fails with an exception. In general, if <tt>build.source.changes</tt> is empty, a URL should be constructed from the platform and other variables appropriate to the build | ||
* '''Make a paster template for buildbot testing:''' As a generalization, the production [http://hg.mozilla.org/build/buildbot-configs/ buildbot configs] are less appropriate for testing and developing Mozilla's buildbot. A template could be created to make it easier to make testing master and slave instances. Files should include <tt>master.cfg</tt>, a script for (re)starting both master and slave | * '''Make a paster template for buildbot testing:''' As a generalization, the production [http://hg.mozilla.org/build/buildbot-configs/ buildbot configs] are less appropriate for testing and developing Mozilla's buildbot. A template could be created to make it easier to make testing master and slave instances. Files should include <tt>master.cfg</tt>, a <tt>forcebuild</tt> script for the buildslave, and a script for (re)starting both master and slave and forcing a build. The template additionally serves as instructions for future generations. | ||