Re: javac compiler errors

Wouldn't it be better if Jenkins would already provide a feature to visualize compile errors? (And plug-ins can add new patterns for new compiler types?) I can add such a feature in the warnings plug-in, however I think it would make more sense to have that part in Jenkins core… Currently my

Jenkins vs. EBCDIC

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

Re: Jenkins vs. EBCDIC

This should work out of the box, because we take the encoding of the slave into account for obvious reasons. the Execute Shell feature uses the CommandInterpreter class, which uses the FilePath.createTextTempFile method to create a shell script. This file takes contents as String, then uses the

Re: javac compiler errors

I think it would be very helpful to have this as part of Jenkins core. Christoph Ulli Hafner ullrich.haf...@gmail.com schrieb: Wouldn't it be better if Jenkins would already provide a feature to visualize compile errors? (And plug-ins can add new patterns for new compiler types?) I can add

Jenkins and Git

Hi, I'm new to Jenkins and reasonable new to Git and I'm trying a simple initial check but get this... Started by user me Building in workspace D:\applications\jenkins\jobs\myProject\workspace Checkout:workspace / D:\applications\jenkins\jobs\myProject\workspace -

Pull requests not being picked up by Pending Pull Requests wiki page?

Hi - I'm working on what I'm convinced is an orphaned pluginhttps://github.com/jenkinsci/shelve-project-plugin-plugin/, based on an older pull request and some Jira tickets that have gone uncommented/unaddressed for some time. I also posted a topic a couple days ago asking about this, and

Re: H cron syntax - How to specify between 10 pm and 6 am?

This should work: 00 22-06 * * * However, I believe this would run at the top of every hour between 10pm and 6am.  If you are just wanting it to run once, I would just specify the time you want it to run every day.  Something like: 00 02 * * * So, 2am every day -

Re: H cron syntax - How to specify between 10 pm and 6 am?

Woops, didn't even notice the random option of H somehow... With that, the syntax you have appears to be correct.  Is there a JIRA ticket in for this maybe already? - Original Message - From: k thieling k.thiel...@comcast.net To: jenkinsci-users@googlegroups.com Sent:

Re: email-ext

Is there anything in the Jenkins logs? regards, slide On Wed, Jun 12, 2013 at 5:36 AM, Welsh, Neil welsh...@visa.com wrote: ** Hi All, I am having an issue with the email-ext plug-in in that it has stopped working :S. this has only started since the end of may. it seems as though

RE: Struggling to launch Windows 7 64-bit slave

This problem is now fixed. Best regards David From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of David Aldrich Sent: 11 June 2013 16:50 To: jenkinsci-users@googlegroups.com Subject: Struggling to launch Windows 7 64-bit slave Hi We are struggling to

Re: Jenkins vs. EBCDIC

Ah, the default encoding. It seems we *have* to set it to something other than EBCDIC so we can even get a connection to our master. The slave is connected via Java Web Start and started like so: java -Dfile.encoding=ISO8859_1 -jar slave.jar -text -jnlpUrl

RE: Jenkins vs. EBCDIC

Looks like jenkins serves up its JNLP pages without an XML prolog (the ?xml version=1.0 encoding=UTF-8? bit)... 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-users@googlegroups.com

H cron syntax - How to specify between 10 pm and 6 am?

Hi, I would like to specify a job to start once a day, between 10 pm and 6 am. This: H H(22-6) * * * is not accepted: Invalid input: H H(22-6) * * *: line 1:9: 1 is an invalid value. Must be within 1 and -15 What is the correct syntax? -- dave -- View this message in context:

Re: Jenkins vs. EBCDIC

XML without prolog is parsed as UTF-8, so I think that part is OK. I'm spotting a few places in JNLP handshaking that relies on ASCII-compatible encoding, so I wonder if that's causing it. In any case, I think we need more detailed error messages. Another thing I spotted is the BASIC auth

Re: Jenkins vs. EBCDIC

I claim f8916a839c5a7bfe6d0de100a33cf23de33de6e4 in the remoting fixes that. Any chance you can try a new remoting jar to see if you can connect via JNLP without overriding the encoding? There's a corresponding change in the server for a proper fix, but you wouldn't need that since your master

Re: Struggling to launch Windows 7 64-bit slave

Can you post your fix in case it helps future users. On Tuesday, June 11, 2013 11:49:39 AM UTC-4, David Aldrich wrote: Hi We are struggling to launch a Windows 7 64-bit slave. Our master is on Centos 5 and we have successfully launched Win XP 32-bit slaves and Win XP 64-bit slaves.

Perforce plugin- What is te log entry mean

Hi Using Jenkins 1.509.1 with Perforce plugin 1.3.19 I've seen this for a long time, but now seems like a good time to ask... My Jenkins log is full of entries like this: Jun 12, 2013 12:39:21 PM com.tek42.perforce.parse.AbstractPerforceTemplate login WARNING: Using p4 issued ticket.

Maven build failures not detected by Jenkins

Hi, Background We are migrating from a legacy build system to Jenkins. So, our build boxes already are configured for various tools (e.g. Maven). Problem The Jenkins job has an Invoke top-level Maven targets build step that compiles code, etc. When there are compile errors (or other errors