That is interresting usecase indeed. It is hard to create a UI that addresses all the scales. I think you arn't doing anything wrong, but you are doing unusual things.
I think you can use a custom buildpage template. I would not advice to build you own custom web UI, as this is eventually a lot of work, and that would contribute to the fragmentation of buildbot. What we support is custom templates: via the custom_templates_dir of c['www'] *http://docs.buildbot.net/latest/manual/cfg-www.html <http://docs.buildbot.net/latest/manual/cfg-www.html>* You would need to customize the buildpage, and probably also the buildsummary In order to create what you are asking, probably also you would need a customcss, which I think is not possible yet. Another idea for a contribution! :) Le jeu. 4 févr. 2016 à 22:07, Greg MacDonald <[email protected]> a écrit : > Hi Pierre, > > > > Attached are some png screenshots. It’s just very spammy and I’m not sure > how I should be using the name and describe properties. There’s also a mix > of old style operations that have both descriptionDone and regular > description. The new ones take a list of short descriptions. It’s > complicated and I’m not sure what to do. > > > > What you’re seeing is name set to a sentence and description and > descriptionDone not set at all. This ends up being less spammy than when I > had the descriptions set. Before I had name set to foo_bar but that tended > to not add anything of value IMHO. > > > > Thx for taking a look. > > > > -Greg > > > > > > *From:* Pierre Tardy [mailto:[email protected]] > *Sent:* Thursday, February 04, 2016 10:44 AM > *To:* Greg MacDonald; [email protected] > *Subject:* Re: [[email protected]] metadata properties > > > > Hi Greg, > > > > Could you share one or two screenshot showing your issues, because I have > to admit I am a little bit lost understanding what you are trying to > achieve. > > > > > > > > Le jeu. 4 févr. 2016 à 01:37, Greg MacDonald <[email protected]> > a écrit : > > So I’ve switch to using the name step attribute as a sort of title for > each build step and it looks a lot nicer. I’ve also cleared the two > description attributes because I’m not sure what they add. Maybe it’s best > to let the base classes put info in there? Still feels like these should be > in a metadata attribute to me. > > -Greg > > > > *From:* users [mailto:[email protected]] *On Behalf Of *Greg > MacDonald > *Sent:* Wednesday, February 03, 2016 1:54 PM > *To:* [email protected] > *Subject:* [[email protected]] metadata properties > > > > Hi Everyone, > > > > For the build UI page I don’t understand why the a class property is used > as the main line for the build step. My users don’t care that it’s a p4 > step or a shell command, they’d rather see something like, “Generating > Meshes” and pretty much only that with some timing info and status. They > also don’t care about build properties. But I need that info while I work > with the system. Same goes for the skip/hide properties. I’m setting some > properties to large lists which end up printing text all over the screen in > a very ugly manner. I could hide it, but I need that info. > > > > So I’m going to have to rewrite this for our purposes, which is fine. I’m > really starting to enjoy coffeescript and angular. But it leads me to think > that perhaps visual properties like step descriptions, skips, and hides > should be kept separate from the main system. Someone could rewrite the > entire UI and then those properties end up being unnecessary. I think some > separation of concerns might be good. How about we add an optional metadata > property which contains a dictionary? The web pages could pick it up and > use it for whatever they needed. It decouples things and allows third party > UI to have their users add per step properties, or any of the objects in > the data model. > > > > On a related note the issue I had with builder names being restricted to > 20 characters with the dataService api wouldn’t matter so much. And having > an internal terse name makes it easier for me to develop as well, saving > the flowery more verbose stuff for the visuals. > > > > -Greg > > _______________________________________________ > users mailing list > [email protected] > https://lists.buildbot.net/mailman/listinfo/users > >
_______________________________________________ users mailing list [email protected] https://lists.buildbot.net/mailman/listinfo/users
