Closed
Bug 1330999
Opened 7 years ago
Closed 7 years ago
Turn off all Win10 support in Buildbot
Categories
(Infrastructure & Operations Graveyard :: CIDuty, task)
Infrastructure & Operations Graveyard
CIDuty
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: catlee, Assigned: spacurar)
Details
Attachments
(4 files)
9.39 KB,
patch
|
kmoir
:
review+
aselagea
:
checked-in+
|
Details | Diff | Splinter Review |
12.54 KB,
text/plain
|
Details | |
1.57 KB,
patch
|
kmoir
:
review+
aselagea
:
checked-in+
|
Details | Diff | Splinter Review |
17.30 KB,
patch
|
kmoir
:
review+
aselagea
:
checked-in+
|
Details | Diff | Splinter Review |
All efforts for Windows10 support will be in Taskcluster. Let's remove win10 support from buildbot, puppet, cloud-tools, etc.
Updated•7 years ago
|
Assignee: nobody → sebastian.pacurar
Assignee | ||
Comment 1•7 years ago
|
||
Attachment #8827416 -
Flags: review?(kmoir)
Comment 2•7 years ago
|
||
Attaching tests diff.
Comment 3•7 years ago
|
||
Do we also need to remove win10 entries from puppet and cloud-tools? Aren't they needed for running jobs in TC?
Comment 4•7 years ago
|
||
Comment on attachment 8827416 [details] [diff] [review] bug1330999_bbconfigs.patch Thanks! I think this is your first patch if I'm not mistaken so congratulations Sebastian!
Attachment #8827416 -
Flags: review?(kmoir) → review+
Reporter | ||
Comment 5•7 years ago
|
||
(In reply to Alin Selagea [:aselagea][:buildduty] from comment #3) > Do we also need to remove win10 entries from puppet and cloud-tools? Aren't > they needed for running jobs in TC? I don't think TC uses these repositories in any way for Win10. Rob, can you confirm?
Flags: needinfo?(rthijssen)
Comment 6•7 years ago
|
||
i confirm that tc win 10 jobs have no dependencies on cloud-tools or puppet.
Flags: needinfo?(rthijssen)
Comment 7•7 years ago
|
||
Thanks for confirming! Sebastian will upload the remaining patches tomorrow.
Updated•7 years ago
|
Attachment #8827416 -
Flags: checked-in+
Assignee | ||
Comment 8•7 years ago
|
||
Attachment #8827909 -
Flags: review?(kmoir)
Assignee | ||
Comment 9•7 years ago
|
||
Attachment #8827910 -
Flags: review?(kmoir)
Updated•7 years ago
|
Attachment #8827909 -
Flags: review?(kmoir) → review+
Comment 10•7 years ago
|
||
Lots of things to undo from bug 1304065, and probably others. Eg slavealloc slave entries, repurpose h/w (eg t-w1064-ix), remove AWS instance t-w10-spot-001 if there's nothing to save (currently that's just stopped).
Updated•7 years ago
|
Attachment #8827910 -
Flags: review?(kmoir) → review+
Comment 11•7 years ago
|
||
Judging from the key name, t-w10-spot-001 (currently stopped) was launched by Q :) Is there anything that needs to be saved from this server? Or it can simply be terminated?
Flags: needinfo?(q)
Comment 12•7 years ago
|
||
Comment on attachment 8827909 [details] [diff] [review] bug1330999_puppet.patch https://hg.mozilla.org/build/puppet/rev/9155129eb0d3 https://hg.mozilla.org/build/puppet/rev/20a8baa738b0
Attachment #8827909 -
Flags: checked-in+
Comment 13•7 years ago
|
||
Created a PR corresponding to the cloud-tools patch reviewed by Kim above: https://github.com/mozilla-releng/build-cloud-tools/pull/278 I will need to ask someone to merge it when you have some spare time. Thanks!
Comment 14•7 years ago
|
||
All t-w10-spot and g-w10-spot were deleted from slavealloc.
Updated•7 years ago
|
Attachment #8827910 -
Flags: checked-in+
Comment 16•7 years ago
|
||
Yeah, the work here is done. There's one more ni to see if t-w10-spot-001 can be terminated, but I guess we can mark this bug as fixed and keep the ni since it's not urgent.
Status: NEW → RESOLVED
Closed: 7 years ago
Flags: needinfo?(aselagea)
Resolution: --- → FIXED
Updated•6 years ago
|
Product: Release Engineering → Infrastructure & Operations
Updated•4 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•