[JIRA] [core] (JENKINS-35174) Modify cloud API when several shared clouds are defined with the same label

2016-05-27 Thread elliot.wei...@gmail.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Elliot Weiser commented on  JENKINS-35174 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Modify cloud API when several shared clouds are defined with the same label  
 
 
 
 
 
 
 
 
 
 
Thanks for opening this Félix Belzunce Arcos. Distributing load across clouds would be very desirable. To your point about "expensive" versus "cheap" clouds, there are a number of load balancing algorithms that are potentially worth pursuing (all of which have their merits): 
 

Round Robin
 

Weighted Balance
 

Least Used
 

Least (Current) Load
 
 
I'll try to poke at the source code in my spare time to see what's feasible. I have a picture in my head of how it could work. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [mask-passwords-plugin] (JENKINS-34264) Mask Passwords does not enable variables in workflow/pipeline

2016-05-02 Thread elliot.wei...@gmail.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Elliot Weiser commented on  JENKINS-34264 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Mask Passwords does not enable variables in workflow/pipeline  
 
 
 
 
 
 
 
 
 
 
Then what is the point of the `var` variable? Performing this assignment seems like a no-brainer to me. What I expected was a `withEnv` step called under the covers that assigned the masked string to environment variables. While it is true that we could do this ourselves, it looks dirty, the true usage of it is opaque (see my first question), and it puts the burden on the person writing the pipeline script. 
While it is true that the credentials binding plugin helps link environment variables to secrets, it requires that there be a stored credential per secret. An example use-case in which this is insufficient is repository-based secrets, whereby a single credential is kept in a domain that is then used for decrypting secrets stored in a git repository and storing them as "masked passwords". As I mentioned before, withCredentials demands a credential per secret. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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.