Wall of status

[thibaultduponchelle]

A new page to list all status for a bitbucket project, github org, module namespace etc...

I do this kind of thing, it's a bit hacky and dirty but it is working for a user point of view.
Here is my homemade thing :

buildbot has a page that looks like this, but he mixing workers with status (matrix commit/worker).

[melezhik]

Sorry, could you please clarify how this relates / used in Sparky?

[thibaultduponchelle]

It's a UI only thing.
It requires a new "view".

I want to monitor the build statuses of a github organization, bitbucket project or list of modules as a whole.

Therefore I want a page where all these build status appears "compact".

I don't really care about building the information "does the same config/code builds on multiple platforms" ? (what I said above for buildbot)

We could even put a "summary" on top like this :

[melezhik]

so in other word you want a page with build statuses per ORG/Project ? (GH orgs, BB projects).

Like:

GH Org1           GH Org2             BB project
repo1 status     repo1_status        repo1_status
repo2 status     repo2_status        repo2_status
repo3 status     repo3_status        repo3_status

And on

I don't really care about building the information "does the same config/code builds on multiple platforms" ?

How would you decide if a build ( without platform knowledge ) is succeeds, If say for one platform it fails and for other it succeeds ?

[thibaultduponchelle]

Yes exactly !

But it could be also all modules from a module namespace (e.g. all GETOPT::* modules)
(Or an arbitrary list)

For the platforms, I'm very concerned about it, I just wanted to highlight that this is not this particular "portability" use case that I want to see here.
But it could of course be either used to calculate the overall succeed/failure of one item or we can make it appear beside in the same view. I even have an homemade example (2 platforms with different installer):

[thibaultduponchelle]

I have an idea for this (and for some other issues), I need to take time to develop, but I think I have a solution :)