Submitting Data

To submit your test data to Treeherder, you have two options:

  1. Using Taskcluster (recommended)

    It’s strongly recommended that you schedule jobs using Taskcluster rather than using your own build system, since otherwise many Treeherder features will not work without significant effort, and it’s also unlikely your jobs will be eligible for tier 1 or even tier 2 status.

  2. Using Pulse

    This is the process Taskcluster is using to submit data to Treeherder. There is a Pulse Job Schema to validate your payload against to ensure it will be accepted. In this case, you create your own Pulse exchange and publish to it. To get Treeherder to receive your data, you would create a bug to have your Exchange added to Treeherder’s config. All Treeherder instances can subscribe to get your data, as can local dev instances for testing.

    While it is beyond the scope of this document to explain how Pulse and RabbitMQ work, we encourage you to read more about this technology on its Wiki page.

    Note: Support for submitting data using Pulse outside of Taskcluster may be removed in the future.

If you are establishing a new repository with Treeherder, then you will need to do one of the following:

  1. For GitHub repos: Adding a GitHub Repository
  2. For Mercurial repos: Add a new Mercurial repository

Using Pulse

To submit via a Pulse exchange, these are the steps you will need to follow:

1. Format your data

You should format your job data according to the Pulse Job Schema, which describes the various properties of a job: whether it passed or failed, job group/type symbol, description, log information, etc. You are responsible for validating your data prior to publishing it onto your exchange, or Treeherder may reject it.

2. Create your Exchange

With Pulse Guardian, you need to create your Pulse User in order to create your own Queues and Exchanges. There is no mechanism to create an Exchange in the Pulse Guardian UI itself, however. You will need to create your exchange in your submitting code. There are a few options available for that:

  1. MozillaPulse
  2. Kombu
  3. Or any RabbitMQ package of your choice

To test publishing your data to your Exchange, you can use the Treeherder management command publish_to_pulse. This is also a very simple example of a Pulse publisher using Kombu that you can use to learn to write your own publisher.

3. Register with Treeherder

Once you have successfully tested a round-trip through your Pulse exchange to your development instance, you are ready to have Treeherder receive your data.

Treeherder has to know about your exchange and which routing keys to use in order to load your jobs.

Submit a Treeherder bug with the following information:

{
    "exchange": "exchange/my-pulse-user/v1/jobs",
    "projects": [
        'mozilla-inbound._'
    ],
},

Treeherder will bind to the exchange looking for all combinations of it and the projects. For example with the above config, we will only load jobs from the mozilla-inbound._ project.

If you want all jobs from your exchange to be loaded, you can use the # wildcard like so:

"projects": [
    '#'
],

If you want one config to go to Treeherder Staging and a different one to go to Production, please specify that in the bug. You could use the same exchange with different project settings, or two separate exchanges. The choice is yours.

4. Publish jobs to your Exchange

Once the above config is set on Treeherder, you can begin publishing jobs to your Exchange and they will start showing in Treeherder.

You will no longer need any special credentials. You publish messages to the Exchange YOU own. Treeherder is now just listening to it.

Adding a GitHub Repository

The pushes from GitHub repos come to Treeherder via Pulse. The webhook to enable this exists in the GitHub group mozilla. (For example, github.com/mozilla/treeherder)

The following steps are required:

  1. Create a PR with the new repository information added to the fixtures file: treeherder/model/fixtures/repository.json
  2. Open a bug request to enable the webhook that will trigger pulse messages for every push from your repo. Use the following information:
    • Component: GitHub: Administration
    • Ask to install the https://github.com/apps/taskcluster integration on your repositories
    • List the repositories you want to have access to the integration
    • Answer: Are any of those repositories private?
    • State that this is only to get Pulse messages for integration into Treeherder