jenkinsci / jenkinsci/gerrit-trigger-plugin

[JENKINS-30997] Gerrit trigger is not able to connect with gerrit server in jenkins version 1.633

Open
#741 0 comments 0 reactions 0 assignees View on GitHub
component:gerrit-trigger-plugin imported-jira-issue priority:major resolution:unresolved
Dominant language
Java
Stars
226
Forks
289
PR merge metrics
No merged PRs in 30d

Description

I have install gerrit (version 2.11) server. and jenkins (version 1.633)

I have followed the gerrit access right as mention in this link https://wiki.jenkins-ci.org/display/JENKINS/Gerrit+Trigger

i have secified my gerrit server setting in gerrit trigger.

but when i tried to test connection than it's showing error as below:

Connection error : com.jcraft.jsch.JSchException: java.lang.RuntimeException: java.lang.ClassNotFoundException: com.jcraft.jsch.Buffer

But with jenkins version 1.625.1 it's working fine

---
Originally reported by neeraj_kumawat, imported from: Gerrit trigger is not able to connect with gerrit server in jenkins version 1.633


  • status: Open
  • priority: Major
  • component(s): gerrit-trigger-plugin
  • resolution: Unresolved
  • votes: 1
  • watchers: 2
  • imported: 2025-12-06

Raw content of original issue

I have install gerrit (version 2.11) server. and jenkins (version 1.633)
I have followed the gerrit access right as mention in this link https://wiki.jenkins-ci.org/display/JENKINS/Gerrit+Trigger
i have secified my gerrit server setting in gerrit trigger.
but when i tried to test connection than it's showing error as below:
Connection error : com.jcraft.jsch.JSchException: java.lang.RuntimeException: java.lang.ClassNotFoundException: com.jcraft.jsch.Buffer

But with jenkins version 1.625.1 it's working fine

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the Gerrit trigger connection test with Gerrit 2.11 and Jenkins 1.633, comparing it with the working Jenkins 1.625.1 setup. Investigate the reported JSch ClassNotFoundException for com.jcraft.jsch.Buffer; done means the connection test succeeds on the affected version without regressing the older working setup.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
ci-cd, devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.