Re: Jenkins doesn't care that needed JDK is not configured on slave

2014-04-29 Thread Mark Waite
The PlatformLabeler plugin has been a real help for some of those cases of OS and platform values, and it handles them automatically. On Tue, Apr 29, 2014 at 9:42 AM, Jeff wrote: > Maybe this exists but I missed it, but I also wonder if there is a way to > inject system environment variables on

Re: Jenkins doesn't care that needed JDK is not configured on slave

2014-04-29 Thread Kevin Fleming (BLOOMBERG/ 731 LEXIN)
Well, this requires that the slave be accessible, which would not be true for cloud slaves that are spawned on demand :-) It's an interesting idea, but there would need to be some sort of 'mapping' mechanism to take the raw strings from the slave's environment and turn them into suitable labels

Re: Jenkins doesn't care that needed JDK is not configured on slave

2014-04-29 Thread Jeff
Maybe this exists but I missed it, but I also wonder if there is a way to inject system environment variables on any node (master/slaves) so that things like OS name/family, architecture, OS distribution (e.g., 'Ubuntu 14.04 LTS'), etc. could be already available. Seems redundant to have to manual

Jenkins doesn't care that needed JDK is not configured on slave

2014-04-29 Thread karg
As we need a lot of manually installed tools, we decided to have strictly separated slaves and provide rather lots of labels to get each project built on the right slave. This works really good so far. Now we thought we could spare at least the label for the JDK, as Jenkins in a sense has all ne