lambda-ui icon indicating copy to clipboard operation
lambda-ui copied to clipboard

An alternative Graphical User Interface for LambdaCD

Results 26 lambda-ui issues
Sort by recently updated
recently updated
newest added
trafficstars

there are 4 pending pull requests on this project and it doesn't seem to have been maintained for a few months now. @sroidl are you around? @flosell I'm tempted to...

question

The following screenshot states the problem: ![screen shot 2017-05-16 at 13 33 09](https://cloud.githubusercontent.com/assets/2619581/26104016/5c620bf4-3a3c-11e7-9c2b-c3381bcdca81.png) Every

The Lambda-UI always shows errors on the console (this also happens in the example-pipelines): `VM533:35 WebSocket connection to 'ws://localhost:8082/lambdaui/api/builds' failed: Close received after close` The UI functions as expected but...

(def pipeline-def `( manualtrigger/wait-for-manual-trigger some-step-that-does-nothing some-step-that-does-nothing some-step-that-does-nothing some-step-that-does-nothing some-step-that-does-nothing some-step-that-does-nothing some-step-that-does-nothing some-step-that-does-nothing some-step-that-does-nothing some-step-that-does-nothing some-step-that-does-nothing some-step-that-does-nothing some-step-that-does-nothing )) causes ![screen shot 2017-04-12 at 11 42 36](https://cloud.githubusercontent.com/assets/112350/24951716/a5be41b4-1f75-11e7-9857-809b8be468eb.png) The oldstyle UI displays...

Displaying meta-information of a pipeline would be a good feature to allow having more information for the pipeline. One example could be step descriptions, that allow the pipeline creator to...

frontend
backend
epic

When I open an active build step's output there's a good chance that more output keeps coming in. The show output layer scrolls to bottom automatically which is quite annoying...

frontend

setting :show-version to false does not opt-out the version footer completely: ![image](https://cloud.githubusercontent.com/assets/2619581/22386573/019fef7e-e4d8-11e6-9ba7-a6e68def1914.png) Please fix :)

bug
in progress
frontend

Some environments (like proxies etc.) don't support websockets. There should be a fallback mechanism to http when the websocket connection can't be established.

enhancement

Currently we only support updating the clients by polling. This is done via websockets, but we do not leverage the full potential of websockets yet. We should: - Push updates...

backend
epic

When there is no build in a pipeline, I'd like to see a welcome screen. Maybe with a indicator on how to start a new build

frontend