[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jgit-dev] JGit JIPP suddenly has a Windows build slave

This is a great opportunity to change the definition of that job to use JGit instead of command line git.

The failure message is due to the master using '/usr/local/bin/git' as its definition of the location of git. If the administrators of the master use the system configuration UI for the Jenkins Git plugin to add JGit as an implementation, then that job can be modified to use JGit instead of command line git.

Nice side benefit - the JGit project is then using JGit to clone their own repositories in Jenkins. Other side benefit, the undying gratitude of the maintainer of the Jenkins git plugin (me) for the JGit development team.

If someone needs help with the specific details of making that configuration change, I'm happy to help.

Mark Waite

On Tue, Feb 26, 2019 at 2:45 PM Thomas Wolf <thomas.wolf@xxxxxxxxxx> wrote:
Who has added a windows build slave to the JGit JIPP?


Our builds fail on that machine.

I'm all for having a Windows build slave, but can we test that setup first and only let a test job run there until it seems fine?

I have for now restricted the following builds to run only on the JIPP master (Linux):

JGit nightly build: https://ci.eclipse.org/jgit/job/jgit/
JGit stable build: https://ci.eclipse.org/jgit/job/stable/job/jgit-stable/
JGit review build: https://ci.eclipse.org/jgit/job/stable/job/jgit.gerrit/

Once that new build slave actually works with our builds, we can lift the restriction again.


jgit-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

Mark Waite