Closed Bug 1110304 Opened 10 years ago Closed 9 years ago

Apply Mercurial 3.2.1 GPO to windows test farm too

Categories

(Infrastructure & Operations :: RelOps: General, task)

x86_64
Windows Server 2008
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: Callek, Assigned: markco)

References

Details

(Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/4229] )

+++ This bug was initially created as a clone of Bug #1056981 +++

With the GPO in place for builders now, we want to deploy Hg 3.2.1 to the windows test pools as well.

Lets start with (any) 5 testers out of XP, 7 and 8 and just deploy the same GPO stuff.

With a pool as busy as test machines we should know relatively quickly if something is wrong.
Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/4229]
I have disable 001 for xp, 7, and 8 in slave alloc. I will start working on this tomorrow am.  Once the GPO is good to go I will disable through 005 and and reply back here.
Window 7 is worked out. 001 already has it installed. 

I have disabled 005 -008. I will move those over once they are idle.

I am still working on xp and 8.
Windows 7 005 - 008 has been moved to the testing OU.
(In reply to Mark Cornmesser [:markco] from comment #3)
> Windows 7 005 - 008 has been moved to the testing OU.

Mark noticed these were not enabled today, so I moved them to live, and rebooted
I can't (from job logs alone) easily confirm the 3.2.1 hg is being used, however I *can* confirm that hg itself is working fine. So lets move w7 live across the pool
With the holiday tomorrow, I am not comfortable making this move till Monday.
Moving this out to the Windows 7 tester ou now.
Windows 8 is worked out and is being installed to the correct directory. I have disabled 005 through 009. Once their current jobs complete I will move them into the testing OU.
Moved the WIN 8 machines to the testing ou. 

Also I have moved the Win 7 machines back to the proper OU.
XP has been worked out 001 through 005 has been disabled  and moved into the testing OU. 

XP and Win 8. The package should be installed o the next reboot.

I have not re-enabled these machines.
Are you going to reenable them?
What has been done previously is someone on the releng side has re-enable the machines. That way they can keep an eye out and keep the number of burn tests to a minimum, if something goes wrong.
(In reply to Phil Ringnalda (:philor) from comment #11)
> Are you going to reenable them?

My fault, I meant to do this enabling last week, and it slipped my mind... done now

XP's 001-->005 all enabled/rebooted
win8's 005-->009 all enabled/rebooted
Is this something we want to apply to the testing OUs?  I just notice that we still have these machines in test pools.
Ooops, yes. I forgot to followup and look into this. The existing testers all look good!

I'd say today(~now)/tomorrow(~morning) is a great time to deploy this everywhere.
And I commented on the wrong Mercurial bug https://bugzilla.mozilla.org/show_bug.cgi?id=1056981

The GPO has been linked to the XP and Win 8 testing OUs.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.