ReleaseEngineering/Applications/BuildbotBridge: Difference between revisions

ReleaseEngineering/Applications/BuildbotBridge (view source)

Revision as of 13:37, 1 June 2015

2,046 bytes added , 1 June 2015

no edit summary

Bhearsum

canmove, Confirmed users

6,439

edits

@@ Line 9: / Line 9: @@
 * [https://pulse.mozilla.org Pulse] - To subscribe to Taskcluster and Buildbot exchanges
 * [https://secure.pub.build.mozilla.org/buildapi/self-serve Self Serve] - To cancel Builds and BuildRequests
+== Development ==
+To do development of the Buildbot Bridge is it recommended that you run your own versions of each of its components. You will need a few other things before this will work:
+* [https://tools.taskcluster.net/auth/ Taskcluster credentials]
+* [[ReleaseEngineering/How_To/Setup_Personal_Development_Master A Build and/or Test Buildbot master]]
+** You must be running command_runner.py and pulse_publisher.py as well.
+** If you need both, they must be pointed at the same database
+* [[https://pulse.mozilla.org/profile A Pulse account]]
+Once you have those, adjust the config to use them as well as your own provisioner id, worker group, and worker id. For example, here is the config that bhearsum uses:
+<pre>
+{
+    "taskcluster_queue_config": {
+        "credentials": {
+            "clientId": "<redacted>",
+            "accessToken": "<redacted>"
+        }
+    },
+    "buildbot_scheduler_db": "sqlite:////builds/buildbot/bhearsum/build1/master/state.sqlite",
+    "bbb_db": "sqlite:///bbb.db",
+    "pulse_user": "bhearsum-publisher",
+    "pulse_password": "<redacted>",
+    "pulse_queue_basename": "queue/bhearsum-publisher",
+    "allowed_builders": [
+        ".*"
+    ],
+    "tclistener": {
+        "pulse_exchange_basename": "exchange/taskcluster-queue/v1",
+        "worker_type": "buildbot-bridge-bhearsum",
+        "provisioner_id": "buildbot-bridge-bhearsum",
+        "selfserve_url": "http://foo.com/junk",
+        "logfile": "tclistener.log"
+    },
+    "bblistener": {
+        "pulse_exchange": "exchange/bhearsum-publisher/buildbot",
+        "tc_worker_group": "buildbot-bridge-bhearsum",
+        "tc_worker_id": "buildbot-bridge-bhearsum",
+        "logfile": "bblistener.log"
+    },
+    "reflector": {
+        "interval": 60,
+        "logfile": "reflector.log"
+    }
+}
+</pre>
+Note that the selfserve_url is junk. This is because there is no staging vesrion of BuildAPI (like most of the rest of our CI infrastructure), so you'll be unable to test changes that depend on it in dev unless you set-up your own instance.
 == Deployment ==