I had a similar issue with Tomcat running Jenkins. I was able to get
around it with these Java options:
-Xms64m -Xmx256m
But I also downgraded to Java 6. YMMV.
Dave
>
>
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe f
I agree. I just found the iconv utility. I run this as the last steps in
my shell script on any artifacts I want brought back to Jenkins. This
worked beautifully!
Using Jenkins with z/OS opens up a lot of possibilities!
>
>
--
You received this message because you are subscribed to the
Any updates on this? I'm in the same boat. The slave.jar connects just
fine with no special encoding, but any artifacts created on z/OS USS side
come back to the Jenkins server as EBCDIC and so does the log file found on
the server (even though it won't display on the web page).
Thanks!
Dav
Hi jay,
I'm wondering if you ever got a reply to this, or figured out a way to do
this. I'm in the exact same boat. The slave-agent starts just fine and
the Jenkins server can see all the good Node Statistics -- but I don't get
a console log and I create a log.txt as an artifact with comman