Wednesday, January 29, 2014

How to create a new version of mozpoolclient

I thought I had created a post on how to create new version of mozpoolclient, however, I could not find them anywhere. I only found a brief note on our wiki page.

Create a new version & upload to RelEng's Pypi

From the instructions in here:

  1. Make your code changes
  2. Update the version in setup.py 
  3. Add a new line to CHANGES.txt with the new version, the date and what is changing
  4. cd mozpoolclient && python setup.py sdist

Upload to Pypi

NOTE: This only applies to me and dustin as the package maintainers on pypi
  1. Register the app with "python setup.py register"
    • You can read the instructions in here
  2. Build, register, sign and upload
    • python setup.py sdist register upload --sign
  3. When you load the pypi package you should see a green "download" button





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

Monday, January 27, 2014

Mozilla's RelEng squirrel tweets!


 @MozRelEng

Release Engineering's squirrel is going crazy about Releasing Firefox and FirefoxOS and Mozilla's large continuous integration infrastructure.

If you're interested on hearing what the squirrel says, follow her at @MozRelEng and use #releng to get the word about Release Engineering.

To know more about Release Engineering's team visit: https://wiki.mozilla.org/ReleaseEngineering#Team



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

Tuesday, January 21, 2014

Mozilla's pushes for December 2013

This blog post is a continuation of the infrastructure load series that John O'Duinn had been writing since 2009.

For now, I will be doing this every month and I will be providing a new format to help me see the big picture more easily. If there's anything you're missing from the posts that John used to do please let me know.

Feedback very much wanted! :)

Link to the 2013-12 pushes report.

Highlights

  • Pushes/month: 6,063 pushes
    • This is a low number compared to our usual load
      • This is due to developers being off since Dec. 20th
      • We've had over 7000 pushes/month in the last 6 months
        • except October with the summit 
    • Even then, December had more pushes than February and June of 2013
  • Pushes/day: 
    • 196 pushes/day
    • 14 days over 300 pushes
  • Pushes/hour:
    • On average: 9 hours of the day had more than 9 pushes/hour
    • On average: our busiest hours were between 8am and 3pm
    • On average: we had ~12 pushes between 13:00-14:00 Pacific time
  • The top 4 branches were:
    • try (50%)
    • mozilla-inbound (17.4%)
    • b2g-inbound (10.2)
    • fx-team (6.8%)
    • They accounted for 84.4% of all pushes

Observations

  • Since the beginning of the year we have seen a decline on number of pushes for mozilla-inbound
    • This is due that the fx-team and the b2g-inbound trees are sheriff managed trees
  • The new pool of Windows machines were added around May of 2013
    • Two months later we see a substantial growth on the Try tree usage
    • I assume that this helped testing on the Try tree
      • We were under-water-level with our old Windows test pool
      • NOTE: Testing on the Try tree has the lowest priority when scheduling jobs
    • I hope this means that developers saw the Try tree to be useful again

Current records

  • August of 2013 was the month with most pushes (7,771 pushes)
  • August 26th had the highest number of pushes in one day with 443 pushes
  • Our highest average of "pushes-per-hour" is 15.73 pushes/hour



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