[JIRA] (JENKINS-60361) Distributed builds: schedule build onto fastest available node

2019-12-04 Thread dun...@anca.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Robert D created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60361  
 
 
  Distributed builds: schedule build onto fastest available node   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Martin Spielmann  
 
 
Components: 
 schedule-build-plugin  
 
 
Created: 
 2019-12-04 09:12  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Robert D  
 

  
 
 
 
 

 
 In a distributed system with multiple permanent build nodes, I would like a scheduling strategy option that favours the fastest available node so that I can get the build and test results sooner.  This could be based on simple cpu or disk bencharks, or based on previous build times, or both.  A custom distributed testing system we created uses a simple hashes/second metric to select the fastest agent for tests to run on. TeamCity has some performance score for agent selection, although I'm not sure how it's calculated.   One simple use case is where a new node is introduced to an on-premisis build system, and the old nodes are kept for spare capacity.  With the current strategy, builds are still performed on the old node. Our use case involves many nodes, both fast and slow, with mutiple labels for environment/tools/production etc. and nodes servicing several labels, and we often find builds on slow nodes when fast ones that match the labels are sitting idle.  
 

  
 
 
 
 

 
 
 

 
 
   

[JIRA] (JENKINS-48504) Lightweight checkout fails when Pipeline JenkinsFile is in a subfolder

2018-09-18 Thread dun...@anca.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Robert D commented on  JENKINS-48504  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Lightweight checkout fails when Pipeline JenkinsFile is in a subfolder   
 

  
 
 
 
 

 
 Robin Smith, I no longer see the lightweight checkout error with plugin version 2.2.11 (on Jenkins 2.107). The build's console output shows "Obtained subdir/Jenkinsfile from ", unsure if that is from BBSP or another plugin. Since we're no longer getting the lightweight error with the FileNotFoundException, and our atlassian-bitbucket.log is showing the correct "GET .../subdir/Jenkinsfile" request format, I can confirm this is fixed for us.  
 

  
 
 
 
 

 
 
 

 
 
 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.