Skip to content
No description or website provided.
Python Shell
Find file
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.
configs bug 1244219 bustage workaround; r=me a=sheriff
examples bug 1001720 - mozharness examples. r=rail
external_tools Bug 1139066 part 2: Add support to download configs from git remotes.
mozfile bug 965519 - add mozprocess v0.15 to mozharness. r=jgriffin
mozharness Bug 1176466 - Add test summary regex for mozmill tests. r=jlund
mozinfo bug 965519 - add mozprocess v0.15 to mozharness. r=jgriffin
mozprocess Bug 1160650 - Backport bug 950894 to mozharness' version of mozproces…
scripts bug 1193011 - bustage in save all mapfiles to logs; r=me
test Bug 1130336 - Create a function to determine: total, used and free di…
.gitignore Backed out changeset ce13a8b349ac (re-enabling mozharness 0.4)
.hgignore bug 1151954 backout - needs to be in-tree; r=bustage
.hgtags Added FIREFOX_40_0b8_RELEASE FIREFOX_40_0b8_BUILD1 tag(s) for changes…
.travis.yml Bug 1186397 - Try to use encrypted variables to prevent travis IRC sp…
LICENSE bug 650890 - port remote talos to mozharness. p=callek r=aki bug 1239003 - repo only for non-gecko apps now; r=jlund
requirements.txt Updated the requirements.txt with dependencies for push_apk
setup.cfg Bug 1076810 - fix mozharness nosetests failures by introducing a setu… Bug 984888 - bouncer submitter should run for every build attempt of …
tox.ini bug 918055 - b2g branching script with revision locking. r=rail


If you are viewing this from git, this repository is a read-only downstream copy of

The mozharness repository is only used for 2 projects at this time:

All other uses of MozHarness are "in tree" of gecko repositories, in the testing/mozharness directory.

Submitting changes

Please contact the application developers via the above links to find their contribution process.


To run mozharness unit tests

pip install tox

To run tests in travis

Please note if you fork this repository and wish to run the tests in travis, you will need to enable your github fork in both travis and coveralls. In both cases you can log in with your github account, you do not need to set up a new one. To enable:

After enabling, you will need to push changes to your repo in order for a travis job to be triggered.

To match commits to upstream hg changesets

Add this following section to the .git/config file in your local clone:

[remote "mozilla"]
    url =
    fetch = +refs/heads/*:refs/remotes/mozilla/*
    fetch = +refs/notes/*:refs/notes/*

then to match a git commit to an upstream hg changeset:

git fetch mozilla
git log

This will produce output like this:

commit c6dc279ab791d7cd11ccc57d2d83a61dc5e0dd09
Author: Simarpreet Singh <>
Date:   Mon Dec 22 14:46:56 2014 -0500

    Bug 1078619 - Allow to run talos jobs as a developer. r=armenzg

    Upstream source:

commit dce9aae0dadf3875afd44c8e61b70fd5ba91f91f
Author: Ankit Goyal <>
Date:   Mon Dec 22 10:18:16 2014 -0500

    Bug 1113081 - Remove references to metro mode from script. r=jmaher

    Upstream source:

commit 7bc17c00dafb144b9982dff2e19e8da91229c6c5
Author: Peter Moore <>
Date:   Fri Dec 19 20:35:55 2014 +0100

    Bug 1076810 - coveralls publish failures should not cause travis job result to be failure,r=rail

    Upstream source:

This allows you to map a git commit SHA to an hg changeset SHA ("Upstream source").

Happy contributing! =)

Something went wrong with that request. Please try again.