[JIRA] (JENKINS-59051) Tool type "jgit" does not have an install of "jgit" configured

8 views
Skip to first unread message

james@howeswho.co.uk (JIRA)

unread,
Aug 22, 2019, 8:36:03 AM8/22/19
to jenkinsc...@googlegroups.com
James Howe created an issue
 
Jenkins / Bug JENKINS-59051
Tool type "jgit" does not have an install of "jgit" configured
Issue Type: Bug Bug
Assignee: Mark Waite
Components: git-plugin
Created: 2019-08-22 12:35
Environment: Jenkins 2.176.2
Git Plugin 3.12.0
Labels: pipeline
Priority: Major Major
Reporter: James Howe

The Declarative Directive Generator gives this for using a configured JGit tool

tools {
  jgit 'jgit'
}

However, it doesn't actually work

Tool type "jgit" does not have an install of "jgit" configured - did you mean "null"?

The same happens for the Apache HTTP variant.
Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

mark.earl.waite@gmail.com (JIRA)

unread,
Aug 22, 2019, 11:12:03 AM8/22/19
to jenkinsc...@googlegroups.com
Mark Waite assigned an issue to Unassigned
Change By: Mark Waite
Assignee: Mark Waite

mark.earl.waite@gmail.com (JIRA)

unread,
Aug 22, 2019, 11:33:01 AM8/22/19
to jenkinsc...@googlegroups.com
Mark Waite commented on Bug JENKINS-59051
 
Re: Tool type "jgit" does not have an install of "jgit" configured

The issue is in the declarative syntax generator or possibly in the class structure of the git client plugin. The syntax:

tools {
  git 'jgit'
}

should work. Unfortunately, I detect no difference in log output or behavior no matter what syntax I use for the `git` tool in the `tools` directive. I see the same output whether I use:

tools {
  git 'Default'
}

or

tools {
  git 'git-windows' // I have a git-windows installer configured which runs a specific path of git on Windows
}

That may be why the docs only list `maven`, `jdk`, and `gradle`. The syntax helper offers values for `git` but they seem to either be ignored or be so subtle that I'm not seeing what I expect in the output.

mark.earl.waite@gmail.com (JIRA)

unread,
Aug 22, 2019, 11:34:04 AM8/22/19
to jenkinsc...@googlegroups.com
Mark Waite updated an issue
 
Change By: Mark Waite
Component/s: workflow-basic-steps-plugin
Component/s: git-plugin

mark.earl.waite@gmail.com (JIRA)

unread,
Aug 22, 2019, 11:36:06 AM8/22/19
to jenkinsc...@googlegroups.com
Mark Waite edited a comment on Bug JENKINS-59051
The issue is in the declarative syntax generator or possibly in the class structure of the git client plugin.  The syntax:
{noformat}
tools {
  git 'jgit'
}
{noformat}


should work.  Unfortunately, I detect no difference in log output or behavior no matter what syntax I use for the `git` tool in the `tools` directive.  I see the same output whether I use:

{noformat}
tools {
  git 'Default'
}
{noformat}

or

{noformat}

tools {
  git 'git-windows' // I have a git-windows installer configured which runs a specific path of git on Windows
}
{noformat}

That may be why the [docs|https://jenkins.io/doc/book/pipeline/syntax/#tools] only list `maven`, `jdk`, and `gradle`.  The syntax helper offers values for `git` but they seem to either be ignored or be so subtle that I'm not seeing what I expect in the output.

If I use a multibranch pipeline and define the git implementation in the multibranch pipeline as 'jgit', then jgit is used to generate the declarative pipelines in that multibranch pipeline.

mark.earl.waite@gmail.com (JIRA)

unread,
Aug 22, 2019, 11:45:02 AM8/22/19
to jenkinsc...@googlegroups.com
Reply all
Reply to author
Forward
0 new messages