Thank you for an example.
I try that.
I see EnvVars have information about its platform.
I plan to manage platform-dependent variable handling with it.
Regards,
ikedam
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from t
Hello,
You can find example here:
https://github.com/jenkinsci/cygwin-process-killer-plugin/blob/master/src/main/java/com/synopsys/arc/jenkinsci/plugins/cygwinprocesskiller/CygwinProcessKiller.java
On the slave:
- you can get channel to master via SlaveComputer.getChannelToMaster().
-
On Sun, Oct 6, 2013 at 2:26 AM, Ikedam wrote:
> I think it can be done by modifying behaviors of EnvVars.
Be very careful here. From what I understand, the design is that an
EnvVars keeps track of whether it is supposed to be used on Unix
(case-sensitive) or Windows (case-insensitive), and these
Thanks for reply.
But I don't plan to do as proposed way.
Handling variables case-insensitive could be harmful, especially when
launching native processes
(I'm so irritated with this behavior...).
I try a way that case-insensitive variables will be available only when a
user intends it explicit
Hi, I am not sure if there is a way of making EnvVars case-sensitive
without breaking existing setups. How about making the class
case-sensitive internally and when resolving particular key prefer exact
matches over the insensitive ones?
Given that we have:
TEST=UC_TEST
test=lc_test
PATH=/b
Hello.
I'm now working with JENKINS-16255
(https://issues.jenkins-ci.org/browse/JENKINS-16255),
which is a problem that Jenkins does not handle environments variables
case-sensitive.
I think it can be done by modifying behaviors of EnvVars.
I want Jenkins have an option whether to handle variab
