So, basically tooltool on windows slaves is not up to date, this prevent us from using the unpack feature for zip files as it is quite new. So we are kind of looking at workaround because of that in two bugs at least: https://bugzilla.mozilla.org/show_bug.cgi?id=1234500 https://bugzilla.mozilla.org/show_bug.cgi?id=1236624 It's not good that we are starting to look at workarounds (possibly in different directions) here. If possible, it would be best to update the installed tooltool on slaves, so everyone can benefit of the tooltool features without reinventing the wheel. So maybe puppet can help, https://github.com/mozilla/build-puppet/blob/master/modules/packages/templates/tooltool.py.
Everything that uses puppet is up to date -- it's just the non-puppet windows stuff that remains. Mark, is it easy to take the latest tooltool.py linked above and get it onto those remaining hosts?
Component: RelOps: Puppet → RelOps
QA Contact: dustin → arich
It should be straight forward. Replacing the source file on the domain.
Should this be tested before roll out?
This particular version has been in use for a long time on linux/mac with no issues. Aside from testing the rollout itself, I think it doesn't need any testing.
I'll do a small roll out test in the am. Followed by a full deployment.
This is now going out to Windows Testers. As far as builders we should have them worked out shortly, within days, to update from Puppet.
Are the puppet manifests all written for this so that, as soon as we turn puppet on, the changes will roll out?
(In reply to Amy Rich [:arr] [:arich] from comment #7) > Are the puppet manifests all written for this so that, as soon as we turn > puppet on, the changes will roll out? Yes.
All of the Windows platforms except b-2008 should currently have the new tooltool.py. We are beginning to to test the b-2008 golden AMI creation with Puppet, so we will start seeing the new tooltool on that segment of machines shortly.
This is now going out to b-2008 as well.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → FIXED
Is this also available on the try instances? (re: https://bugzilla.mozilla.org/show_bug.cgi?id=1236624#c5)
It appears to be. I just compared tooltool.py from a y instance with the new one being pushed out to the domain machines and the file was identical.
You need to log in before you can comment on or make changes to this bug.