Hi Everybody, we run a Jenkins 1.532 *Build master* which uses the SSH Slave plugin to communicate with two *Build slaves* (CentOS 6.4 machines). In our configuration the Build slaves are dumb, the Java JDK 1.7 and Maven 3.0.5 is provided by the master. This works, the Build master is able to start jobs on the slaves.
We have some serious problems with the used encoding on the *Build Slaves*. We are using some files in our test resources with UTF-8 characters in it's names (japanese, chinese and arabic) which leds in the current setup to build failures. If we look at the System properties provided by Jenkins (Jenkins > nodes > Buildnode > Systeminformation) these settings are given: *System Settings* file.encoding = ANSI_X3.4-1968sun.jnu.encoding = ANSI _X3.4-1968 *Environment Variables* _/usr/bin/javaHOME/home/jenkinsLOGNAMEjenkinsMAIL/var/mail/jenkinsNLSPATH /usr/dt/lib/nls/msg/%L/%N.catOLDPWD/home/jenkinsPATH /usr/local/bin:/bin:/usr/binPWD/var/lib/jenkinsSHELL/bin/bashSHLVL1... USERjenkinsXFILESEARCHPATH/usr/dt/app-defaults/%L/Dt We tweaked the CentOS system settings and if we run "env", we get HOSTNAME=build2 SHELL=/bin/bash TERM=xterm HISTSIZE=1000 LC_ALL=en_US.UTF-8 USER=jenkins LS_COLORS=rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:mi=01;05;37;41:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arj=01;31:*.taz=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.dz=01;31:*.gz=01;31:*.lz=01;31:*.xz=01;31:*.bz2=01;31:*.tbz=01;31:*.tbz2=01;31:*.bz=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.rar=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.jpg=01;35:*.jpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.axv=01;35:*.anx=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=01;36:*.au=01;36:*.flac=01;36:*.mid=01;36:*.midi=01;36:*.mka=01;36:*.mp3=01;36:*.mpc=01;36:*.ogg=01;36:*.ra=01;36:*.wav=01;36:*.axa=01;36:*.oga=01;36:*.spx=01;36:*.xspf=01;36: MAIL=/var/spool/mail/jenkins PATH=/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin PWD=/home/jenkins LANG=en_US.UTF-8 HISTCONTROL=ignoredups SHLVL=1 HOME=/home/jenkins LOGNAME=jenkins CVS_RSH=ssh LESSOPEN=|/usr/bin/lesspipe.sh %s G_BROKEN_FILENAMES=1 _=/bin/env OLDPWD=/home/jenkins As you can see the file.encoding and sun.jnu.encoding are different and Jenkins does not recognize the LANG system variable. The result is it is possible to run the build from the command line on the *Build slave* successfully, the same job started by Jenkins fails. Starting the slave with JVM arguments -Dfile.encoding=UTF-8 etc. did not help, the plugin EnvInject seems not to help either. The key question is: why are the environment settings not taken correctly by Jenkins? Any help is appreciated, Christoph -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
