-
Bug
-
Resolution: Unresolved
-
Minor
-
None
Actual: When the Gerrit trigger was enabled in the Jenkins, it triggered all the old check-ins which were done before enabling the Gerrit trigger.
Expected: When the Gerrit trigger is enabled in the Jenkins, it should trigger only the new check-ins which are done after enabling the Gerrit trigger.
Gerrit trigger plugin version: 2.34.0
Gerrit code review version: 2.14.7
Gerrit trigger setting configuration:
gerrit-trigger:
servers:
- config:
buildCurrentPatchesOnly:
abortManualPatchsets: false
abortNewPatchsets: false
abortSameTopic: false
enabled: false
categories: - verdictDescription: "Code Review"
verdictValue: "Code-Review" - verdictDescription: "Verified"
verdictValue: "Verified"
gerritAuthKeyFile: "/usr/share/jenkins/secrets/gerrit"
gerritFrontEndUrl: "https://example.com/gerrit3/"
gerritHostName: "example.com"
gerritHttpPassword: "****"
gerritHttpUserName: "jenkins"
gerritSshPort: 29420
gerritUserName: "jenkins"
restCodeReview: true
useRestApi: true
name: "user01"
noConnectionOnStartup: true