chocolatey
Package specific ability to adjust the execution timeout
Some packages already know they take over an hour or more to install. Wouldn't it be nice if the package could request longer periods for install?
Of course it can't be done in automation scripts because by the time those run the value is already locked in stone and counting down. So that leaves either a nuspec enhancement #325 or a special file that could be found in the package
Original conversation with @tcase:
UPDATE: As Chocolatey Gitter chat is now unavailable, I've added a screenshot of the Gitter chat.
This is something that would certainly provide more resiliency for end users. It just took sas94 over 1.5 hours with just one machine hitting the server. Could be as simple as another optional parameter (I like the idea of a special file that choco would look for in the path after extraction but before time starts? not looked at code for this yet) that would set the timeout to the greater of local config and package config. Probably be nice to put an extra warning message if it is set higher than local config so that user knows what to expect. Also restore to previous local config regardless of success or failure.,
Added security as we'd see this as an opt-in thing to allow passing over to the package to control something normally controlled by the end user.
We would want to add a check to Package Validator for a maximum timeout value that could be set for packages being submitted to the Chocolatey Community Repository.
A new feature (to opt-in / out for every run), and an option to both skip it from a run or to include it for a run, should be added.
