Job execution timeout setting
Reported by Alex-SF | May 2nd, 2011 @ 06:36 PM
Add an attribute to a Job definition, specifying the maximum time duration for job execution. This sets an upper limit for how long will run.
Comments and changes to this ticket
-
Deleted User May 2nd, 2011 @ 08:28 PM
- Milestone order changed from “28” to “0”
Would this override the framework.properties or would it be subject to framework properties. Also...it might be worth putting the timeout on the command/exec or command/script and not on the overall job.
-
Alex-SF June 8th, 2011 @ 08:32 AM
- Milestone cleared.
-
Alex-SF July 9th, 2011 @ 01:53 PM
- Tag set to “feature request, timeout”
-
celinedion July 31st, 2023 @ 02:48 AM
Jobs with potential issues or infinite loops can be automatically terminated by the system when the timeout is reached. This prevents job bottlenecks and driving directions maintain system stability.
-
rosy23dam August 1st, 2023 @ 01:59 AM
My sincere thanks go to the author for only up! their contribution in providing readers with practical and beneficial knowledge.
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
(DEPRECATED) Please use github issues for issue tracking at http://github.com/dtolabs/rundeck/issues
Alex-SF
Greg Schueler
Tristan Rivoallan