This repository has been archived by the owner. It is now read-only.
Trigger Jenkins jobs for B2G builds between revisions
Switch branches/tags
Nothing to show
Clone or download
Pull request Compare This branch is even with mozilla:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.


b2ghaystack is a tool to assist in searching for B2G regressions by triggering jobs in Jenkins for each build between two revisions.


You must have a Jenkins instance running that you can reach with at least one job configured with the following parameters:

  • BUILD_REVISION - This will be populated with the revision of the build that will be tested.
  • BUILD_TIMESTAMP - A formatted timestamp of the selected build for inclusion in the e-mail notification.
  • BUILD_LOCATION - The URL of build to download.
  • APPS - A comma separated names of the applications to test.
  • NOTIFICATION_ADDRESS - The e-mail address to send the results to.


With pip and git installed you can use:

pip install git+git://

If you anticipate modifying b2ghaystack, you can instead:

git clone git://
cd b2ghaystack
python develop


usage: b2ghaystack [-h] [-v] [--dry-run] [-m MAX_BUILDS] [-b BRANCH] [--eng]
                   [-a [APP [APP ...]]] [-u USERNAME] [-p PASSWORD]
                   [-j JENKINS_URL] [-e EMAIL]
                   device_name job_name good_rev bad_rev

Trigger Jenkins jobs for all builds between revisions.

positional arguments:
  device_name         name of device
  job_name            name of the jenkins job to execute
  good_rev            last known good revision
  bad_rev             first known bad revision

optional arguments:
  -h, --help          show this help message and exit
  -v, --verbose       verbose output
  --dry-run           output the jobs to console without triggering them
  -m MAX_BUILDS       maximum number of builds to trigger (default: 10.0)
  -b BRANCH           branch to use (default: mozilla-central)
  --eng               limit to engineering builds
  -a [APP [APP ...]]  names of applications to test
  -u USERNAME         username for access to the builds
  -p PASSWORD         password for access to the builds
  -j JENKINS_URL      url of jenkins instance (default: http://localhost:8080)
  -e EMAIL            email address to send result notifications