![]() |
|
|
|
|
Issue Type:
|
![Improvement]() Improvement
|
|
Affects Versions:
|
current |
|
Assignee:
|
Nicolas De Loof
|
|
Components:
|
slave-prerequisites |
|
Created:
|
09/Feb/13 9:23 AM
|
|
Description:
|
By incident we noticed that when replacing a master with a different one (in turn this means we moved the local .jenkins folder on the slave), the Jenkins master creates a new (second!) windows service.
This is rather untypical on Windows. A service is typically serving all instances at once, the idea of one service per instance is untypical.
To sum up, it would be great if the service would simply be called "Jenkins", and serve both folders.
A second service would only be needed in case the two masters want to run different user accounts. In that case, it makes more sense to name the Jenkins slave services not by installation folder but by master's host name.
Or even better, provide a "CI domain name" to the master, and use that one.
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Markus KARG
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[email protected].
For more options, visit
https://groups.google.com/groups/opt_out.
