mtabara> rail: to be honest, I can't recall what we wanted in 1407333. do you remember more details? was it that various configs that are both in mozharness configs and in project_branches are unified in the same place? 22:07:58 <aki> probably make it so we don't have to clone buildbot-configs for that info 22:08:10 <aki> just guessing 22:10:16 <mtabara> hm, that'd make sense. however, although slightly easy to implement, that's not something to change over night. I'll investigate though to see what that would mean 22:16:25 <aki> yeah. i'm not sure it's worth the time, since ideally we move off bb onto tc sooner. but if it's doable quickly it might be worth it 22:16:45 <aki> it might save us some bb-c edits on esr52 22:21:42 <rail> mtabara: I'd probably rename it to something like "find and get rid of duplicate configs"

So I spent some time today to identify some of the configs that are duped. In the meantime, I had the chance to get a glimpse on how the future looks like and how in-tree scheduling looks like (currently Fennec on maple). I'm still digging but so far I reached :aki's conclusion as well. It's just not worth investing the time to move some of the configs (e.g. https://hg.mozilla.org/build/buildbot-configs/file/tip/mozilla/project_branches.py#l413) within simply the in-tree configs. In-tree scheduling solves this problem in a much cleaner way and the only benefit here long term really is esr52. I'll keep digging but fwiw, I think we should just WORKSFORME this bug for now.

Agreed in the meeting today that we can close this bug for now as the real benefit is minimal. We'll focus on the future!