Juha

Currently the polling mechanism to check pipeline run status is not working reliably. Often when you click "run" on long running task the UI will just show it in "running"...

How to reproduce: - Open pipelines - Make your API unreachable - Click Run - Expected: - See error that can't run the task - What happened - I see...

Currently the log lines are not html escaped which leads to some unexpected formatting in some cases:  We should properly escape the log lines. The color highlighting may currently...

**Expected behaviour** Pipelines should create status.json with status failed if the schema check fails Also other exceptions when running tasks seem to not update status.json. We should have catch-all around...

Currently the UI doesn't represent http error responses properly. We should check that we have error handling at least for: - Getting pipelines fails - Running pipeline fails - Getting...

Implement simple cron support within the API to run pipelines periodically. Tasks: - Define the trigger-format - Choose suitable library (hopefully tornado-centric) - Implement the scheduler. Should be on the...

Currently when you run a pipeline the UI will poll the logs endpoint until it finishes. This means every time it will fetch all of the logs which is far...