lumio / wallboard Goto Github PK

Well obviously this project needs a CONTRIBUTING file

Do you want to request a feature or report a bug?
feature

The current theme looks fine for smaller groups. But when working in larger companies, it might be better to have a more compact UI. E.g. like https://github.com/BBVA/mirrorgate

Instead of having a rather variable width set for the hearts, define groups where only full or half hearts are filled in red.

These groups should be something like this:

[ 0, 35, 51.65, 70, 85.45, 100 ]

That means that everything under 20% should get 0 hearts.

Currently there are no real tests implemented

Do you want to request a feature or report a bug?
feature

The communication between Jenkins and wallboard is currently a bit messy. A better way to deal with this is to use the jenkins package

Do you want to request a feature or report a bug?
feature

Reload config as soon as it has been changed

Hello folks! 😄

Leave a comment on what CI/CD should be supported.

Depending on the comment reactions I'm going to try and support additional CI/CDs

Do you want to request a feature or report a bug?
bug

What is the current behavior?
When a build was completed but another one started right afterwards, no events get emitted.

What is the expected behavior?
An event should be emitted each time a build was committed

Do you want to request a feature or report a bug?
bug

What is the current behavior?
When new jobs are added/removed the UI breaks

Do you want to request a feature or report a bug?
bug

What is the current behavior?
A job is only visible if it fits a certain pattern. It doesn't matter if the folder is visible or not.

What is the expected behavior?
Jobs should always be visible when folder is too.

Do you want to request a feature or report a bug?
feature

It would be nice to see if any updates are available and kind of allow automatic updates

Do you want to request a feature or report a bug?
bug

What is the current behavior?
If an error occured, only [object Object] is visible

What is the expected behavior?
It should show the error object and refresh after a few seconds

Do you want to request a feature or report a bug?
feature

As mentioned in #28 it might be a good idea to add a plugin system that allows others to create their own sections, showing other services.

Do you want to request a feature or report a bug?
bug

What is the current behavior?
When wallboard fetches a job that was never built, the status and health becomes undefined which crashes the UI.

What is the expected behavior?
Better use 'unknown' if a status is not specified.

Log at least static requests

Currently the backend won’t start with a faulty config file.

Given the fact that the server is probably run in the background it is hard to tell why it doesn’t start unless of course you look into the logs.

Why not showing the error in the browser as well?

Do you want to request a feature or report a bug?
feature

Because Travis is one of the most used CIs in the Open Source community, let us support it as well.

Allow event handlers to be set in the config file.
That way it would be possible to call a third party interface or just run a local command.

{
  // ...
  "events": {
    "event name": {
      "build status": "fetch http://localhost:555"
    }
  }
}

Possible event names: build-change, build-start, build-finish
Possible build status: successful, failed, aborted

Do you want to request a feature or report a bug?
bug

What is the current behavior?
Progress is always negative when notbuilt

Show count of open pull requests

Config proposal:

{
  "pull-requests": string | string[]
}

Each item points to a repository

Although creating a simple config.json is really not that hard - it might be really convenient to have an init script that creates a config file for us

Hi, would be cool to have a section for quotes.

Do you want to request a feature or report a bug?
bug

What is the current behavior?
Currently when a job is building, each pull emits a new change event. This is unnecessary and just consumes ressources.

What is the expected behavior?
Just emit a change as soon as a build status/activity or the available job list has changed.

Add an additional option for themes to enable/disable certain gimmicks.

{
  "theme": {
    "enablePulse": true | false // should disable the pulse effect
    // ...
  }
}

Add a pm2 section explaining on how to run wallboard as a daemon.

Currently typedefs are rarely been used.