The git client 1.19.6 has been running since 3/22/2016 on the master
without errors, so it seems the feature to detect the jdk works as desired,
at least when run on the master. The class version issue only shows up
when we configure the job to run on a slave, It is also interesting that
the
You're correct that git client plugin 1.19.6 includes a jar file that is
compiled with JDK 7. The JGit support for symlinks requires it. However,
that jar file should not be loaded if it is running on a Java 6
environment. The JGit implementation is designed to allow the Java 7
module to only be
That is a shame. I wont be able to move up to Git plugin 2.4.4. until the git
client issue is resolve. I realize you cannot reproduce, and I’m about to
leave for two weeks of well deserved vacation, so I won’t be able to pick this
up again for a while, but if someone else starts reporting issu
Git plugin 2.4.0 requires at least git client plugin 1.18.0.
Git plugin 2.4.4 requires at least git client plugin 1.19.6.
Mark Waite
On Thu, Mar 31, 2016 at 1:22 PM Michael Giroux wrote:
> Reverted Git Client to 1.18.0 and problem is resolved. The notifyCommit
> no longer faults, and the job
Reverted Git Client to 1.18.0 and problem is resolved. The notifyCommit
no longer faults, and the job is running on the slave.
Current config: Git plugin 2.4.0, Git client 1.18.0.
Michael
On Thursday, March 31, 2016 at 11:18:54 AM UTC-7, Mark Waite wrote:
>
> I don't know how to duplicate ei
In the interest of determining if the issue is related to the git client
plugin, I would like to roll back to the previous version. We currently
have 1.19.6 installed. Our previous version was 1.18.0.
Should this combination work? Git Plugin 2.4.0 (or 2.4.4) with Git Client
1.18.0.
Michael
Here are a few more facts that might give some clues.
Master is running Jenkins 1.609.3 in Oracle JDK 1.6.0_75
Slave is Linux running Oracle JDK 1.8.0_20
Git Plugin version 2.4.0
Git Client version 1.19.6
I modified the job configuration to restrict execution to a different slave
(one that it h
I don't know how to duplicate either your issue or JENKINS-33907. I
installed a Jenkins 1.609.3 last night with Java 6, then used a slave with
Java 7, and confirmed that I was able to checkout on the master and the
slave using the command line git implementation with git plugin 2.4.4 and
git clien
Seems another user has similar issue.
https://issues.jenkins-ci.org/browse/JENKINS-33907
That is not exactly the same, but I've seen the same issue, and it could be
related to my issue.
On Tuesday, March 29, 2016 at 11:44:15 AM UTC-7, Michael Giroux wrote:
>
> Since updating to Git plugin vers
Since updating to Git plugin version 2.4.4, our jobs that execute on a remote
slave are failing. The full stack trace from the polling log is below.
Do we need to install additional software on the slaves to accommodate the
update?
Michael Giroux
Polling for changes in
ERROR: Failed to r
10 matches
Mail list logo
