jenkinsci / jenkinsci/gerrit-trigger-plugin
[JENKINS-53738] Gerrit Trigger not triggering jobs with older Gerrit configuration (tag dynamicGerritProjects is missing).
- Dominant language
- Java
- Stars
- 226
- Forks
- 289
- PR merge metrics
- No merged PRs in 30d
Description
Scenario
Start Jenkins 2.138.1 with Gerrit Trigger plugin 2.27.7, everything configured properly, NO jobs.
Import jobs from old Jenkins 1.642.1 with Gerrit Trigger plugin 2.18.3 and restart Jenkins.
Our Review- and Deploy-Jobs do not get triggered from Gerrit Trigger plugin after committing changes for review to Gerrit or after submitting such changes.
Observed
The imported old config.xml files do not have tag . After opening and saving the configuration of these jobs this tag is added and they are triggered again.
---
Originally reported by just_meyer, imported from: Gerrit Trigger not triggering jobs with older Gerrit configuration (tag dynamicGerritProjects is missing).
rsandell
Raw content of original issue
Scenario
Start Jenkins 2.138.1 with Gerrit Trigger plugin 2.27.7, everything configured properly, NO jobs.
Import jobs from old Jenkins 1.642.1 with Gerrit Trigger plugin 2.18.3 and restart Jenkins.
Our Review- and Deploy-Jobs do not get triggered from Gerrit Trigger plugin after committing changes for review to Gerrit or after submitting such changes.
Observed
The imported old config.xml files do not have tag <dynamicGerritProjects class="empty-list"/>. After opening and saving the configuration of these jobs this tag is added and they are triggered again.
- environment:
Jenkins 2.138.1, Gerrit Trigger 2.27.7
Contributor guide
Research direction
Start with the imported job config.xml files and the missing dynamicGerritProjects tag, comparing configurations from Gerrit Trigger 2.18.3 and 2.27.7 under the listed Jenkins versions. Reproduce the migration and triggering scenario, then verify that imported Review and Deploy jobs trigger without opening and saving their configuration.
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
- Mostly clear
- Newbie friendliness
- 25/100