can send me that log file
> and build.xml?
>
> Also, give us the whole stack trace for that error, not just the error
> message, please.
>
>
> 2013/6/17 Dirk Haun <68k...@gmail.com>
>
>> Thanks for making me check the logfile :)
>>
>> Indeed, it
It
> should contain console log in EBCDIC, then you should see
> CP037 (or something like that) in build.xml.
>
>
> 2013/6/13 Dirk Haun <68k...@gmail.com>
>
>> Thanks.
>>
>> The good news: We can now connect the slave without having to set the
>> file.
e - it's simply empty.
Any ideas?
On Thu, Jun 13, 2013 at 2:20 PM, Kohsuke Kawaguchi wrote:
> No, it's not. I created https://ci.jenkins-ci.org/job/remoting/lastBuild/
>
>
> 2013/6/13 Dirk Haun <68k...@gmail.com>
>
>> Kohsuke,
>>
>> thanks for tryi
; ** **
>>>
>>> If you save the file and add an XML prolog for UTF-8 and run from that
>>> without setting the encoding – does that work?
>>>
>>> ** **
>>>
>>> /James
>>>
>>> ** **
>>>
>>> *From:* jenkinsci-user
as String, then uses the encoding of the slave when it does
> "new FileWriter(f)". So it should write the shell script in EBCDIC.
>
> Does your slave JVM have a proper default encoding configured?
>
>
>
> 2013/6/12 Dirk Haun <68k...@gmail.com>
>
>> We&
We're trying to use Jenkins to build our software on OS/390 (using the
Hercules emulator, not real hardware, but still). This OS uses EBCDIC as
its native character set, not ASCII. We've successfully managed to check
out from our SVN repository (yay!), but now we would need to run commands
to build
The changelog for the last couple of LTS releases is empty on the website:
--- snip ---
What's new in 1.424.6 (2012/03/06)
What's new in 1.424.5 (2012/03/05)
What's new in 1.424.4 (2012/03/05)
What's new in 1.424.3 (2012/02/27)
upgrade Apache Maven Wagon to 2.0 (issue 11164)
--- snip ---
