gps pointed out in http://gregoryszorc.com/blog/2013/07/16/analysis-of-firefox%27s-build-automation/ that we use ensure => latest for mozilla-built packages like Python and Mercurial. Really, we should be specifying an explicit version there, so that it's easy to go back in hg history and use an older version, even when new versions are available in the repo.
Created attachment 8411280 [details] [diff] [review] pin package versions for mozilla-build packages This pins versions for: centos: mozilla-git mock_mozilla mozilla-python27-mercurial mozilla-python27-virtualenv mozilla-python26 mozilla-python27 ubuntu: python2.7 python2.7-dev
Comment on attachment 8411280 [details] [diff] [review] pin package versions for mozilla-build packages versions were taken from: b-linux64-ix-0001.build.releng.scl3.mozilla.com talos-linux64-ix-001.test.releng.scl3.mozilla.com
Attachment #8411280 - Flags: review?(dustin)
Comment on attachment 8411280 [details] [diff] [review] pin package versions for mozilla-build packages Did this run without issue on a test slave? That'd be my only worry - that something funny in the way some AWS hosts are built will make this explode. That'd be a good thing to learn, but not via an explosion.
Attachment #8411280 - Flags: review?(dustin) → review+
I tested on a datacenter test node and an aws test node. No changes. Checked in to default: https://hg.mozilla.org/build/puppet/rev/d63ba3e98632
merged to prod
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.