Details
-
Improvement
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Fixed
Description
Currently the service starts in the "Automatic" mode, so there can be conflicts with other services like login service, shared directory mappers, etc. "Automatic (Delayed start)" could resolve this issue by allowing other services to start before Jenkins master/slave starts the initialization.
The change requires https://github.com/kohsuke/winsw/releases/tag/winsw-1.17 at least (not merged into Jenkins core)
Attachments
Issue Links
- is duplicated by
-
JENKINS-43575 Windows service agents and master should use the delayed start option
-
- Resolved
-
I still think that a default delayed start would be preferable for users, who would like to get a working infrastructure out-of-the-box. All service configuration steps may require much time from users, who have no appropriate qualification.
My proposals: