gecko-dev/testing/mozharness
Gregory Szorc 6f813399e5 Bug 1362148 - Always collect build metrics; r=ted
Previously, mozharness defined a separate action to collect build
metrics. This required the script and/or config to define that
action.

Metrics collection for CI is important. So it should be enabled by
default.

This commit changes the "build" action/method to always call the
metrics collection function after successful build. References to
the "generate-build-stats" action have been removed because it is
redundant.

A side-effect of this change is we may generate build metrics where
we weren't before. This could lead to e.g. duplicate entries in some
Perfherder series. Let's see what breaks ;)

MozReview-Commit-ID: 42UQI5YQTMC

--HG--
extra : rebase_source : c57dc9ec6ac46003384edff098a0ad81c75539b7
extra : source : c9812dd7d27a174c0ee46d44ec595fbe29c9e1db
2017-05-04 12:28:52 -07:00
..
configs Bug 1362148 - Always collect build metrics; r=ted 2017-05-04 12:28:52 -07:00
docs Bug 1359988 - Remove mozharness docs related to gaia; r=mshal 2017-04-26 13:55:10 -07:00
examples
external_tools Bug 1317594 - Vendor latest robustcheckout extension; r=me 2017-04-11 13:35:42 -07:00
mozfile
mozharness Bug 1362148 - Always collect build metrics; r=ted 2017-05-04 12:28:52 -07:00
mozinfo
mozprocess
scripts Bug 1362148 - Always collect build metrics; r=ted 2017-05-04 12:28:52 -07:00
test Bug 1330837 - Remove functionality to apply and push; r=aki 2017-04-11 14:23:00 -07:00
LICENSE
mach_commands.py Bug 1263230 - Remove in-tree references to IPC/OOP reftest modes. r=ahal 2016-11-07 08:59:49 -05:00
README.txt
requirements.txt Bug 1330837 - Use Mercurial 4.1 in mozharness tests; r=aki 2017-04-11 14:26:29 -07:00
setup.cfg
setup.py
tox.ini Bug 1330837 - Use Mercurial 4.1 in mozharness tests; r=aki 2017-04-11 14:26:29 -07:00
unit.sh

# Mozharness

## Docs
* https://developer.mozilla.org/en-US/docs/Mozharness_FAQ
* https://wiki.mozilla.org/ReleaseEngineering/Mozharness
* http://moz-releng-mozharness.readthedocs.org/en/latest/mozharness.mozilla.html
* http://moz-releng-docs.readthedocs.org/en/latest/software.html#mozharness

## Submitting changes
Like any Gecko change, please create a patch or submit to Mozreview and
open a Bugzilla ticket under the Mozharness component:
https://bugzilla.mozilla.org/enter_bug.cgi?product=Release%20Engineering&component=Mozharness

This bug will get triaged by Release Engineering

## Run unit tests
To run the unit tests of mozharness the `tox` package needs to be installed:

```
pip install tox
```

There are various ways to run the unit tests. Just make sure you are within the `$gecko_repo/testing/mozharness` directory before running one of the commands below:

```
tox                            # run all unit tests
tox -- -x                      # run all unit tests but stop after first failure
tox -- test/test_base_log.py   # only run the base log unit test
```

Happy contributing! =)