Apply Mercurial 3.2.1 GPO to windows test farm too

RESOLVED FIXED

Status

RESOLVED FIXED
4 years ago
4 years ago

People

(Reporter: Callek, Assigned: markco)

Tracking

Details

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

(Reporter)

Description

4 years ago
+++ 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.

Updated

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

Comment 1

4 years ago
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.
(Assignee)

Comment 2

4 years ago
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.
(Assignee)

Comment 3

4 years ago
Windows 7 005 - 008 has been moved to the testing OU.
(Reporter)

Comment 4

4 years ago
(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
(Reporter)

Comment 5

4 years ago
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
(Assignee)

Comment 6

4 years ago
With the holiday tomorrow, I am not comfortable making this move till Monday.
(Assignee)

Comment 7

4 years ago
Moving this out to the Windows 7 tester ou now.
(Assignee)

Comment 8

4 years ago
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.
(Assignee)

Comment 9

4 years ago
Moved the WIN 8 machines to the testing ou. 

Also I have moved the Win 7 machines back to the proper OU.
(Assignee)

Comment 10

4 years ago
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?
(Assignee)

Comment 12

4 years ago
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.
(Reporter)

Comment 13

4 years ago
(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
(Assignee)

Comment 14

4 years ago
Is this something we want to apply to the testing OUs?  I just notice that we still have these machines in test pools.
(Reporter)

Comment 15

4 years ago
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.
(Assignee)

Comment 16

4 years ago
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
Last Resolved: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.