[JIRA] (JENKINS-33907) Git plugin clone fails on linux slave with Java 1.7

[mark.earl.wa...@gmail.com (JIRA)]

Title: Message Title

Mark Waite edited a comment on JENKINS-33907   Re: Git plugin clone fails on linux slave with Java 1.7 > bq. How about building the git-client plugin producing v51 (java.level=7) bytecode so it will fail fast? (I assume JGit does not work at all and native git might but has problems on important code paths like this) JGit works quite well on a machine which runs Java 6.  The issue is you're running Java 6 on the master and Java 7 on the slave. I'm not willing to break all the Java 6 users who aren't crossing Java version boundaries between master and slaves.  For example, changing from Java 6 byte code to Java 7 byte code would break your installation completely, since you wouldn't be able to load the Java 7 plugin on your Java 6 master. The upcoming git client 2.0 release (and the matching git plugin 3.0 release) will require Java 7 as its minimum version.  A beta release is available from experimental update center.  That beta release requires a minimum of Jenkins 1.625 (the first LTS to drop support for Java 6). Add Comment   This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.