[JIRA] (JENKINS-16731) Common slave service for multiple masters
Title: Message Title Jason Pyeron commented on JENKINS-16731 Re: Common slave service for multiple masters Thoughts on the design pattern: On resource management, the slave has a # of concurrent executors, this value needs to be the same across all masters Can this property be set on the slave and queried by the master, not set? A master should only have detailed job status for its job A master would need to know of a foreign job execution status, at a minimum Job name Job number Master (public/login) URL job start time On authentication The node may want a shared or individual authentication key for each master Individual keys could support an easy way of identifying / tagging jobs to a master? While not needed at first, a queuing ticket issuance for master/master job ordering. Think like a bakery, take a number and wait. For now, think hungry hungry hippos game, if you get the slot, you have a scheduled job - someone will get it and eventually you should get one Are there other ways to minimize the impact/change to the master/node protocol? Add Comment
[JIRA] (JENKINS-16731) Common slave service for multiple masters
Title: Message Title Nicolas De Loof assigned an issue to Unassigned Jenkins / JENKINS-16731 Common slave service for multiple masters Change By: Nicolas De Loof Assignee: Nicolas De Loof Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-16731) Common slave service for multiple masters
Markus KARG created JENKINS-16731 Common slave service for multiple masters Issue Type: 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 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
