[JIRA] (JENKINS-14489) Exclusion per slave

[pr...@electromag.com.au (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Phil R commented on  JENKINS-14489  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Exclusion per slave   
 

  
 
 
 
 

 
 I'd like this feature as well. The Heavy Job plugin kinda works, but you have to keep the number of executors in sync. Which works ok just a bit a maintenance problem.      
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-14489) Exclusion per slave

[m.rou...@gmail.com (JIRA)]

Anthony Roux
 updated  JENKINS-14489


Exclusion per slave
















Change By:


Anthony Roux
(31/Oct/12 8:47 PM)




Issue Type:


Task
NewFeature





Priority:


Major
Minor



























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

[JIRA] (JENKINS-14489) Exclusion per slave

[werni...@java.net (JIRA)]

wernight
 commented on  JENKINS-14489


Exclusion per slave















I found that the Throttle Concurrent Builds Plugin does this in a lesser measure. It cannot have only a small part but it can achieve most of the desired effect.



























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

[JIRA] (JENKINS-14489) Exclusion per slave

[werni...@java.net (JIRA)]

wernight
 created  JENKINS-14489


Exclusion per slave















Issue Type:


Task



Assignee:


Unassigned


Components:


exclusion



Created:


18/Jul/12 4:13 PM



Description:


Nearly all my exclusions are because jobs use a resource shared on that machine but not between machines. So I actually need an exclusion for each slave to avoid the same slave to run the critical block, but two different slave should be allowed to run the critical block.




Project:


Jenkins



Priority:


Major



Reporter:


wernight

























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