Closed Bug 946715 Opened 10 years ago Closed 10 years ago

Migrate w64-ix-slave day7 batch1 to rev2 image

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task)

Product:
Infrastructure & Operations Graveyard
Component:
CIDuty
Platform:
x86
Windows Server 2008
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: jhopkins, Assigned: jhopkins)

References

Details

Attachments

(1 file)

[buildbot-configs] day7 batch1 -> rev2
1.36 KB, patch
bhearsum
: review+
jhopkins
: checked-in+
Details | Diff | Splinter Review 
      No description provided.

        Attachment #8343065 -
        Flags: review?(bhearsum)

    
    

    
  
Comment on attachment 8343065 [details] [diff] [review]
[buildbot-configs] day7 batch1 -> rev2

Review of attachment 8343065 [details] [diff] [review]:
-----------------------------------------------------------------

stamp

        Attachment #8343065 -
        Flags: review?(bhearsum) → review+

    
    

    
  
Comment on attachment 8343065 [details] [diff] [review]
[buildbot-configs] day7 batch1 -> rev2

https://hg.mozilla.org/build/buildbot-configs/rev/4d4c1027b48f

        Attachment #8343065 -
        Flags: checked-in+

    
    

    
  
in production

    
    

    
  
day7 batch1 machines are in production as rev2's.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED

    
    

    
  
These slaves all have staging keys on them. Currently fixing them up.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---

    
    

    
  
These should be fixed now.
Status: REOPENED → RESOLVED
Closed: 10 years ago → 10 years ago
Resolution: --- → FIXED

    
    

    
  
I messed up 139 - 157 the first time - I thought I read this patch as them being try slaves. They've got the proper keys on them now.
Component: Platform Support → Buildduty
Product: Release Engineering → Infrastructure & Operations

    
  
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard

          You need to log in
          before you can comment on or make changes to this bug.