We've been building the ICS emulator on Taskcluster for a while now, though it's been hidden in treeherder. Bug 1208643 is addressing the treeherder issue, so I think we can turn off the duplicate buildbot builds soon.

:sdeckelmann - any idea if we still need ICS emulator nightlies? Or do we need the buildbot ICS emulator builds on any of the release branches until 1208643 rides through?

Naoki -- can you weigh in?

I'm not sure if I understand the situation. Are we talking about removing ICS emulator completely in lieu of kitkat? If that's the question then Ken Chang should probably be able to answer better than I. If you're asking to remove ICS emulator from buildbot and if the taskcluster ICS emulator is working correctly then it's probably safe. Again Ken Chang's team could probably verify this better than I.

We'd still have ICS building in Taskcluster if we shut off buildbot. My questions are: 1) Do we still need the nightly "N" ICS emulator builds? (I don't think we do, but I wanted to double check) 2) Do we need to make sure the Taskcluster ICS builds are in all trees before fully shutting off the buildbot ICS builds? ie: Are they definitely needed in some of the b2g release branches or aurora/beta/etc?

We are still working on migrating to KK emulator and some tests are still run on ICS emulator. If we do this change, will it impact those tests. Need Hsinyi's feedback.

(In reply to Michael Shal [:mshal] from comment #4) > We'd still have ICS building in Taskcluster if we shut off buildbot. My > questions are: > > 1) Do we still need the nightly "N" ICS emulator builds? (I don't think we > do, but I wanted to double check) > Sorry I have no idea about this. > 2) Do we need to make sure the Taskcluster ICS builds are in all trees > before fully shutting off the buildbot ICS builds? ie: Are they definitely > needed in some of the b2g release branches or aurora/beta/etc? I think we need. To be clearer, not just "build", but also "stable" test cases need to be on TC before fully shutting off the buildbot ICS builds. This is because emu-ICS is the only testing environment for certain tests. If we could have either stable ics buildbot or stable ics TC (including test cases), then it's fine. However, I doubt if it's worth stabilizing ics tests on TC at the moment, given that we plan to deprecate emu-ics after migrating to emu-x86-kk.

(In reply to Hsin-Yi Tsai [:hsinyi] from comment #6) > I think we need. To be clearer, not just "build", but also "stable" test > cases need to be on TC before fully shutting off the buildbot ICS builds. > This is because emu-ICS is the only testing environment for certain tests. > If we could have either stable ics buildbot or stable ics TC (including test > cases), then it's fine. However, I doubt if it's worth stabilizing ics tests > on TC at the moment, given that we plan to deprecate emu-ics after migrating > to emu-x86-kk. Ok, then our plan will be to leave ICS on in BuildBot. Given that, do we need the ICS builds in TaskCluster at all? Could we shut these off?

(In reply to Selena Deckelmann :selenamarie :selena from comment #7) > (In reply to Hsin-Yi Tsai [:hsinyi] from comment #6) > > > I think we need. To be clearer, not just "build", but also "stable" test > > cases need to be on TC before fully shutting off the buildbot ICS builds. > > This is because emu-ICS is the only testing environment for certain tests. > > If we could have either stable ics buildbot or stable ics TC (including test > > cases), then it's fine. However, I doubt if it's worth stabilizing ics tests > > on TC at the moment, given that we plan to deprecate emu-ics after migrating > > to emu-x86-kk. > > Ok, then our plan will be to leave ICS on in BuildBot. > > Given that, do we need the ICS builds in TaskCluster at all? Could we shut > these off? We could, leaving either stable one is fine.

Unassigning for now, since it sounds like we might just be waiting for ICS to go away anyway.

(In reply to Hsin-Yi Tsai [:hsinyi] from comment #8) > (In reply to Selena Deckelmann :selenamarie :selena from comment #7) > > (In reply to Hsin-Yi Tsai [:hsinyi] from comment #6) > > > > > I think we need. To be clearer, not just "build", but also "stable" test > > > cases need to be on TC before fully shutting off the buildbot ICS builds. > > > This is because emu-ICS is the only testing environment for certain tests. > > > If we could have either stable ics buildbot or stable ics TC (including test > > > cases), then it's fine. However, I doubt if it's worth stabilizing ics tests > > > on TC at the moment, given that we plan to deprecate emu-ics after migrating > > > to emu-x86-kk. > > > > Ok, then our plan will be to leave ICS on in BuildBot. > > > > Given that, do we need the ICS builds in TaskCluster at all? Could we shut > > these off? > > We could, leaving either stable one is fine. I have fired bug 1219118 to disable all ics test in TackCluster.