Sounds good. Thank you for the valuable insights. On Tue, Mar 26, 2019 at 5:07 PM Pierre Tardy <[email protected]> wrote:
> Hi, > > I think MacPorts has quite specific huge scale in term of the number > of packages it builds, and optimisations on non rebuilding everything. > > So for this project what would be interesting is to research the best > visualisation for MacPort, rather than making compromises so that it > is useful for everybody. > This does not mean we don't want to make it generic as much as we can, > it is just we want it to be super efficient for macports. > > Having a quality dashboard for macport will still benefit for the > community in term of example of how things can be, and how > customisable Buildbot is. > > Another benefit for Buildbot is that it would be the first project to > be specific for react/vue, and we need to improve the interface for > that. > I would like to have react/vue boilerplate improved, so that the core > of it is extracted in a separate npm package. > This npm package could then be kept when we rewrite the core ui > framework in webpack/typescript. This would be a good oportunity to > make the API evolve for better suit in reactive frameworks. > I already saw some issues with the Collection class in buildbot data > which is not well compatible with vue. > > Regards > Pierre > > Le mar. 26 mars 2019 à 11:26, Mojca Miklavec <[email protected]> a écrit > : > > > > On Tue, 26 Mar 2019 at 10:48, Rajdeep Bharati wrote: > > > > > > Would rewriting the waterfall view (with custom features) using Vue be > one of the goals/stretch goals? > > > And I presume that the plugin will become a part of buildbot core? > > > > I leave that up to Pierre to answer. > > > > > > My personal wish (but I lack some deep insight into buildbot itself) > > would be to have a better waterfall view out of the box, so that other > > projects could benefit as well. > > > > Some of the strange views specific to MacPorts (which builds something > > else in every build on the same builder) would probably be more tricky > > to implement in a generic way, even though ... it might perhaps be > > possible to let the buildbot configuration assign a keyword to each > > build on the fly, and then implement a special view where the user can > > specify a keyword as a filter and buildbot would display just the > > matching builds. > > > > In our case we could specify the port name as the keyword. Other > > projects building from different branches or using different settings > > might specify a keyword like "PR", "development", "stable", "beta", > > etc. And then the user could choose to show just builds matching > > "beta", or just builds matching one specific port in our case. > > > > The ability to quickly show the builds matching a particular commit, > > or the ability to easily jump to the builds done on March 8th 2018 ... > > could also be implemented in a generic way. > > > > Mojca >
