I agree that the delayed start may cause additional delays, but...
- There is one well-known use-case with shared directories
- Another known use case is a Windows event system, which starts as a service. If Jenkins starts before it, we may lose events in monitoring systems
- There is a potential risk for user jobs, because currently Jenkins may start executing them on slave machines without fully initialized services => undefined behavior even for standard Windows CLI tools
My opinion is that the "Delayed start" should be enabled by default. If a user knows what he is doing, he can switch the mode an set dependencies on other services. Would you agree with such approach?
> A delayed start by default (IIRC) will keep a slave offline for 2 minutes. AFAICT there is only a global setting for delayed start and changing this will affect services other than Jenkins.
No, Windows will start "delayed" services shortly after starting other ones with automatic start. AFAIK there's no hardcoded timeout.
> this implies that we should not be using winsw to install itself
Service startup mode can be passed via the configuration XML file, which is being used to instal the Jenkins service