You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like to have some better support for jobs (Docker docs. Currently when having a running job, it shows like this in the GUI:
In the overview the state is "not running" which is a bit confusing, since the job is still running.
In my mind, the implementation could be two ways:
fix the status in the services overview to display the correct state for the service/job
add a new sidebar-entry for jobs, with a page that only displays services which only are global-job or replicated-job.
Background: we heavily rely on jobs to do recurring tasks, which works wonderfully, but we need some kind of way to monitor failed tasks. Currently filtering out is possible by just opening all services that are "not running", but once this scales to a few 10s of services it'll become painfull.
I'm not familiar with Java nor the frontend-language, but I can provide testing for new commits if wanted.
Thank you for the projects, it's working great since we've deployed it a few years ago :)
The text was updated successfully, but these errors were encountered:
Hello,
I'd like to have some better support for jobs (Docker docs. Currently when having a running job, it shows like this in the GUI:
In the overview the state is "not running" which is a bit confusing, since the job is still running.
In my mind, the implementation could be two ways:
Background: we heavily rely on jobs to do recurring tasks, which works wonderfully, but we need some kind of way to monitor failed tasks. Currently filtering out is possible by just opening all services that are "not running", but once this scales to a few 10s of services it'll become painfull.
I'm not familiar with Java nor the frontend-language, but I can provide testing for new commits if wanted.
Thank you for the projects, it's working great since we've deployed it a few years ago :)
The text was updated successfully, but these errors were encountered: