Confirmed users
4,293
edits
ReleaseEngineering/Buildbot Best Practices: Difference between revisions
Jump to navigation
Jump to search
ReleaseEngineering/Buildbot Best Practices (view source)
Revision as of 00:11, 17 November 2010
, 17 November 2010→How to land a patch
| Line 20: | Line 20: | ||
== How to land a patch == | == How to land a patch == | ||
Below is one way to land a patch for a Buildbot master. Your technique may vary, but this will ensure there are no other patches sneaking in with yours, and no local changes. Before doing any of the below, land your patches into the repositories. | Below is one way to land a patch for a Buildbot master. Your technique may vary, but this will ensure there are no other patches sneaking in with yours, and no local changes. Before doing any of the below, land your patches into the repositories. | ||
For older masters (like production-master*, test-master*, talos-master02) the checkouts are typically at <tt>/tools/buildbotcustom/buildbotcustom</tt> and <tt>/builds/buildbot/configs</tt>. For buildbot-master* there are buildbotcustom and buildbot-configs checkouts in <tt>/builds/buildbot/$master</tt>. The following text describes the first case. | |||
* Look for local changes on the master. | * Look for local changes on the master. | ||
cd /tools/buildbotcustom/buildbotcustom | cd /tools/buildbotcustom/buildbotcustom | ||