RelEng - what has changed in the last week

Every week we report changes to our infrastructure in various status meetings and speak them out loud on the Tuesday's planning meeting. The purpose of this blog post is to consolidate changes that have happened over the last week in the Release Engineering infrastructure and that can affect developer's work scenarios. This status updates might not be the way to go but let's see how it goes and how much it helps.

I will try to keep it short and simple. I am purposely not listing *everything* that gets fixed but listing *only* things that are new or that affects your workflow and maybe certain milestones for us.

Please let me know if you have any suggestions on how to improve the format or if it is tooooooo short.

Changes from July 19th to July 26th:

• Do not run automatically talos jobs for try by default
• You can ask your fellow buildduty to run it if you need the talos run
• L10n nightly repacks for Linux 64 and Mac 64
• Running unit tests on the minis by default for all branches
• We are running them in both the minis and the builders. We want to run it only on the minis starting this week
• Changes on how we upload mobile builds
• Space on ftp reclaimed

NOTE: I am using dev.planning and blog posts to compose this post

---

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

Unit tests on the minis - status update

Over the last few months we have been switching to run unit tests on the minis to improve our load and use real users' OS to run our unit tests.

We are now running unit tests on the minis for mozilla-central, try and tracemonkey branches. This change means that we have reduced the load on the builders side from running 22 jobs per push per platform to only 2 jobs per push per platform (the opt build and the debug build). Ask joduinn for how much CPU time we are saving [1].

TraceMonkey is the first project branch to be running on the minis but next week we should have *all* other branches move to the minis as well.

TM is the third most active branch after try and m-c and it accounts for 9% of commits (try 37% & m-c 36%). This means we are now running 82% of our unit tests' load on the minis instead of the builders (this is only for Fedora 32/64-bit and OSX 10.5/10.6 since Windows is not yet moved over).

What comes next?
In the next week we should see all other project branches' unit tests to be run on the minis and cut the load again on the builders' side. This will help us to move more slaves to the try pool where they are most needed.

[1] http://oduinn.com/blog/2010/07/16/infrastructure-load-for-june-2010/

---

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