[JIRA] (JENKINS-57326) Support jgit and jgitapache with Configuration as Code plugin

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

Title: Message Title

Mark Waite created an issue   Jenkins / JENKINS-57326 Support jgit and jgitapache with Configuration as Code plugin Issue Type: Improvement Assignee: Mark Waite Attachments: screencapture-home-markwaite-net-jenkins-configureTools-2019-05-04-07_00_50.png Components: git-plugin Created: 2019-05-04 13:05 Environment: Jenkins 2.164.2 Configuration as code latest release Git plugin 3.10.0 Labels: jcasc-compatibility Priority: Minor Reporter: Mark Waite When I export the configuration as code definition of my Jenkins server that has JGit configured as one of the git implementations, it includes lines like this: tool: git: installations: - home: "git" name: "Default" - home: "jgit" name: "jgit" When I load those lines into configuration as code, it attempts to create a command line implementation of jgit instead of creating the internal implementation of jgit. The result of reloading that configuration looks like this: Add Comment   This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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.