Here’s April’s monthly analysis of the pushes to our Mozilla development trees. You can load the data as an HTML page or as a json file.
- April (as March did) has the highest number of pushes ever.
- We will soon have 8,000 pushes/month as our norm, this seems to be the case this month.
- 8109 pushes
- NEW RECORD
- 270 pushes/day (average)
- NEW RECORD
- Highest number of pushes/day: 414 pushes on April 14, 2014
- 14.8 pushes/hour (average)
- Try continues to have around 50% of all the pushes
The three integration repositories (fx-team, mozilla-inbound and b2g-inbound) account for around 30% of all the pushes
- April 2014 was the month with most pushes (8109 pushes)
- April 2014 has the highest pushes/day average with 270 pushes/day
- February 2014 has the highest average of “pushes-per-hour” is 16.57 pushes/hour
- March 4th, 2014 had the highest number of pushes in one day with 435 pushes
The data collected prior to 2014 could be slightly off since different data collection methods were used.
One nagging question I have is “Where is our CPU time going?”
We can infer that roughly 50% ends up on try server, but is that true? If we are running a subset of builds/tests on try, then maybe it is only 33% of total cpu time.
Maybe a first step is to break down into jobs per branch, ideally # builds, # tests.
We can then later assign an average value of time per job and get an estimate of where our time is going.
As always, thanks for making this data public and accessible!
Yes, definitely graphing cpu time would be great. I'd also like to have a way to graph jobs per branch, not sure how to do that today without sql queries, definitely should be accessible via the ui in the reports.