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
... the documentation does not mention anything about my problem
... there are no open or closed issues that are related to my problem
Description
Failed jobs should simply be stopped and not restart indefinitely.
Expected behaviour
When I deploy a new cron, it should not be triggered unless the period configuration says so.
A failed job should not be restarted automatically unless a specific configuration is set.
Actual behaviour
Failed jobs are restarted automatically when it fails on deploy.
Support guidelines
I've found a bug and checked that ...
Description
Failed jobs should simply be stopped and not restart indefinitely.
Expected behaviour
When I deploy a new cron, it should not be triggered unless the period configuration says so.
A failed job should not be restarted automatically unless a specific configuration is set.
Actual behaviour
Failed jobs are restarted automatically when it fails on deploy.
Steps to reproduce
Because
plop
does not exists, the job must fail.docker stack deploy -c ./compose.yaml test_cron
swarm-cronjob version
v1.13.0
Docker info
Docker Compose config
Logs
Additional info
No response
The text was updated successfully, but these errors were encountered: