[JIRA] (JENKINS-54188) Allow "tool locations" to be configured per Azure Virtual Machine Template

2018-10-22 Thread yun...@microsoft.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Yunge Zhu commented on  JENKINS-54188  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Allow "tool locations" to be configured per Azure Virtual Machine Template   
 

  
 
 
 
 

 
 thanks for reporting the issue. we're evaluating it and update later.  
 

  
 
 
 
 

 
 
 

 
 
 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-54188) Allow "tool locations" to be configured per Azure Virtual Machine Template

2018-10-22 Thread yun...@microsoft.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Yunge Zhu started work on  JENKINS-54188  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Yunge Zhu  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 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-54188) Allow "tool locations" to be configured per Azure Virtual Machine Template

2018-10-22 Thread yun...@microsoft.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Yunge Zhu assigned an issue to Jie Shen  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54188  
 
 
  Allow "tool locations" to be configured per Azure Virtual Machine Template   
 

  
 
 
 
 

 
Change By: 
 Yunge Zhu  
 
 
Assignee: 
 Azure DevOps Jie Shen  
 

  
 
 
 
 

 
 
 

 
 
 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-54188) Allow "tool locations" to be configured per Azure Virtual Machine Template

2018-10-22 Thread median...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nick Jones created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54188  
 
 
  Allow "tool locations" to be configured per Azure Virtual Machine Template   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Azure DevOps  
 
 
Components: 
 azure-vm-agents-plugin  
 
 
Created: 
 2018-10-22 16:38  
 
 
Environment: 
 Azure VM Agents 0.7.4  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Nick Jones  
 

  
 
 
 
 

 
 As we migrate from permanent agent notes towards various types of dynamic agents, one of the challenges has been handling varying tool locations across this fleet of VMs. Jenkins has global tool locations (under /configureTools) and permanent agent nodes can have their own (under /computer/ {agent name} /configure), but Azure VM templates do not support this – meaning the only way to configure tool locations for Azure agents is to rely on the global tool configuration in Jenkins centrally. This would work adequately, but for the fact that the vSphere Cloud plugin, while it does allow tool locations to be configured, does not reload them from previously saved configurations (meaning they are wiped out by any save of the Jenkins configuration, unless explicitly set each time), per JENKINS-41428. The ideal would be if the vSphere Cloud plugin were fixed, but in the meantime, it would be very nice if the Azure VM Agents plugin offered the capability to save per-template tool locations as well. This would allow us to configure tool locations for vSphere agents as the global tool configuration, override it for permanent nodes, and also override it for Azure VM agents. As it is, we must continually reconfigure and resave the vSphere tool locations every time, if we're to be able to use both "cloud" plugins. As background, the reason this is necessary in the first place is because of the varying ways MSBuild 2017 gets installed under the Program Files