How to generate allthethings.json

It's this easy!
    hg clone https://hg.mozilla.org/build/braindump
    cd braindump/community
    ./generate_allthethings_json.sh

allthethings.json is generated based on data from buildbot-configs.
It contains data about builders, schedulers, masters and slavepools.

If you want to extract information from allthethings.json feel free to use mozci to help you!
https://mozilla-ci-tools.readthedocs.org/en/latest/allthethings.html

---

This work by Zambrano Gasparnian, Armen is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License.

mozci 0.2.4 released - Support for intermittent oranges + major bug fixes

Big thanks to vaibhav1994 for his intermittent orange script contribution.

Also thanks to adusca and valeriat for their many contributions in this release.

Release notes

The major feature is being able to analyze data about reported intermittent oranges on bugzilla and give the user the ability to trigger jobs to spot where the regression started (generate_triggercli.py).

A lot of bug fixed and optimizations. I'm only highligthing some from this list: 0.2.3...0.2.4

Highlighted fixes:

• Fixed/improved issues with jobs completed today
• Added builds-4hr support
• allthethings.json gets clobbered after 24 hours
• This prevents relying on an old file
• Drop the need to use --repo-name for all scripts
• his prevents the user having to add a redundant option

Release notes: https://github.com/armenzg/mozilla_ci_tools/releases/tag/0.2.4
PyPi package: https://pypi.python.org/pypi/mozci/0.2.4
Changes: https://github.com/armenzg/mozilla_ci_tools/compare/0.2.3...0.2.4

---

This work by Zambrano Gasparnian, Armen is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License.

Listing builder differences for a buildbot-configs patch improved

Up until now, we updated the buildbot-configs repository to the "default" branch instead of "production" since we normally write patches against that branch.

However, there is a problem with this, buildbot-configs is always to be on the same branch as buildbotcustom. Otherwise, we can have changes land in one repository which require changes on the other one.

The fix was to simply make sure that both repositories are either on default or their associated production branches.

Besides this fix, I have landed two more changes:

1. Use the production branches instead of 'default'
• Use -p
2. Clobber our whole set up (e.g. ~/.mozilla/releng)
• Use -c

Here are the two changes:
https://hg.mozilla.org/build/braindump/rev/7b93c7b7c46a
https://hg.mozilla.org/build/braindump/rev/bbb5c54a7d42

---

This work by Zambrano Gasparnian, Armen is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License.