625979 - Tracking bug for making TBPL the official developer dashboard for Firefox and Fennec

John O'Duinn [:joduinn] (please use "needinfo?" flag)

Reporter

Description

•

14 years ago

This project has been in progress for months now, but I cant find tracking bug for this so filing this. 1) We've used tinderbox.m.o to show status of continuous builds for years. However, tbpl.m.o is a better display of the build-per-checkin world that we now live in. Builds+tests are grouped together by developer checkin, instead of by time (the waterfall chronological approach). At the summit (2010), and several developer meetings, I've asked developers if anyone is still using tinderbox server waterfalls, instead of tbpl. Answer always "no", and usually followed by "no-one using it, so why does RelEng still populate and support it"? 2) All the data sourced to populate tbpl.m.o *used* to be obtained by scraping the HTML on tinderbox server. However, over the last few months, this is being migrated over to instead directly reading from buildbot. This also fixes some intermittent bugs in how scraped data is parsed and displayed in tbpl.m.o. 3) Once tbpl.m.o is no longer scraping anything from the tinderbox server for Firefox & Fennec builds, we can stop sending emails to tinderbox server. We can then also replace those Firefox & Fennec waterfalls with links to the relevant tbpl display. Further we can start cleaning up automation code even further by removing tinderbox specific hacks. During the allhands, we met to determine what still needed to be done. I think I've attached all the remaining bugs here, but if I've missed anything, please add! Note: This does *not* mean we are turning off the Tinderbox Server instance at tinderbox.mozilla.org. This instance is being used by multiple projects at Mozilla, and will continue to be run+supported as usual. (If anything, it should become more responsive as the load from Firefox drops!)

Chris AtLee [:catlee]

Assignee