The execution timeout should be disabled by default

Registered by Pierre LEMMET on 2013-07-10

The execution timeout should be disabled by default. This value (agent 2.0.5) can't be updated as it is not supported by 2.0.5 servers.

Blueprint information

Status:
Not started
Approver:
None
Priority:
Medium
Drafter:
None
Direction:
Needs approval
Assignee:
Didier Liroulet
Definition:
Discussion
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

There is a bug in 2.0.5.x and 2.1.0.1 agent disabling ability to control execution timeout from server. It will be fixed in 2.1 final release.

Controlling execution timeout is a feature already available in 2.1 server and setting it to 0 disable this time out.

I don't think it is a good idea to disable by default this timeout. When a package setup reaches this timeout (120 minutes by default), most of the time, it appends because setup crashes. Setting this timeout to INFINITE results a agent blocked, waiting for the end of a setup which will never end...

If you encounter case when setup take more than 120 minutes, it is better to increase this timeout into server configuration, than setting it to INFINITE.

Regards

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.