On Wed, 8 May 2019 at 21:00, Rajdeep Bharati wrote: > > Hi, > > I created some issues and found some which would be relevant for the project > (as discussed in the IRC meeting): > > https://github.com/buildbot/buildbot/issues/4760 > https://github.com/buildbot/buildbot/issues/4761 > https://github.com/buildbot/buildbot/issues/4709 > https://github.com/buildbot/buildbot/issues/3471 > https://github.com/buildbot/buildbot/issues/3470 > https://github.com/buildbot/buildbot/issues/4750
Thank you. (Nice to see that I'm not the first one requesting these :) I assume that we'll also want to add other items for the rest of the summer to that list? > @Mojca Miklavec Yesterday you mentioned: >> >> 16:33:15 <mojca> regarding the features of the default waterfall view, >> another problem I saw was that unless one of the builds was done recently, >> the builder doesn't even show in waterfall; for example, there is no texlive >> or pplib displayed on https://build.contextgarden.net/#/waterfall And later Pierre said this was a feature :) > However, I am unable to find this problem in > https://nine.buildbot.net/#/waterfall (it's showing the builders not having > recent builds). I'm not sure (it might have been configured in that manner in > nine.buildbot, and not present by default). > > I will try to replicate this issue in my local setup. If you look at https://build.contextgarden.net/#/console you can see that there is a huge number of "fake commits" from one project (from periodic scheduler) after the last build of another project was done. Maybe there's a setting which tells you how many latest builds / commits to fetch when drawing the waterfall view. I didn't try to investigate what limits the number of displayed builders. Now: for me by far more important missing feature is in fact support for filtering on both console and waterfall. Once filtering and removal of old builders gets implemented, this particular issue will be less important. Mojca
