[JENKINS-31843] Gerrit build parameters lost in downstream job if rebuild when using build is parameterized

Plugins:

• gerrit-trigger-plugin


• rebuilder plugin

Environment:

• CJE - 1.609.3.1 (also tested with 1.580.3 so version doesn't seem too important)


• https://github.com/fabric8io/docker-gerrit (gerrit environment - checkout and run scripts in instructions section to setup)


• gerrit-trigger.xml (attached) (gerrit-trigger-plugin config. keypath needs to change to where docker-gerrit is checked out)


• upstream job (attached)


• downstream job (attached)

Steps to create gerrit event and trigger plugin:

• Setup project (https://wiki.jenkins-ci.org/display/JENKINS/Gerrit+Trigger#GerritTrigger-SetUp) - only really needs permission for non interactive users. Call project "myproject"


• Checkout, add file, commit, then ammend it to add the Change-Id(Change-Id: I55862204ef71f69bc88c79fe2259f7cb8365699a)


• Push to gerrit - "git push http://admin@​192.168.99.100:8080/myproject HEAD:refs/for/master"


• Make sure upstream and downstream jobs are loaded.


• Use "Query and Trigger Gerrit Patches" to confirm and trigger upstream job


• GOTO: downstream job and "Rebuild last"

Note that "This build is parameterized" makes you re-enter the "test" String parameter.

Also note that when rebuild happens that all the Gerrit build parameters are gone. This doesn't happen when "This buid is parameterized" is removed so suggests that this step is clobbering parameters. But not sure...

Not sure whether the issue is with:

• gerrit-trigger-plugin


• rebuilder plugin


• Jenkins core

but seems like a bug IMO.

---
Originally reported by owood, imported from: Gerrit build parameters lost in downstream job if rebuild when using build is parameterized

• assignee: owood
  
• status: In Progress
  
• priority: Minor
  
• component(s): gerrit-trigger-plugin, rebuild-plugin
  
• resolution: Unresolved
  
• votes: 2
  
• watchers: 3
  
• imported: 2025-12-06
  

Raw content of original issue

Plugins:




	
gerrit-trigger-plugin

	
rebuilder plugin



Environment:




	
CJE - 1.609.3.1 (also tested with 1.580.3 so version doesn't seem too important)

	
https://github.com/fabric8io/docker-gerrit (gerrit environment - checkout and run scripts in instructions section to setup)

	
gerrit-trigger.xml (attached) (gerrit-trigger-plugin config. keypath needs to change to where docker-gerrit is checked out)

	
upstream job (attached)

	
downstream job (attached)



Steps to create gerrit event and trigger plugin:




	
Setup project (https://wiki.jenkins-ci.org/display/JENKINS/Gerrit+Trigger#GerritTrigger-SetUp) - only really needs permission for non interactive users. Call project "myproject"

	
Checkout, add file, commit, then ammend it to add the Change-Id(Change-Id: I55862204ef71f69bc88c79fe2259f7cb8365699a)

	
Push to gerrit - "git push http://admin@192.168.99.100:8080/myproject HEAD:refs/for/master"

	
Make sure upstream and downstream jobs are loaded.

	
Use "Query and Trigger Gerrit Patches" to confirm and trigger upstream job

	
GOTO: downstream job and "Rebuild last"



Note that "This build is parameterized" makes you re-enter the "test" String parameter.

Also note that when rebuild happens that all the Gerrit build parameters are gone. This doesn't happen when "This buid is parameterized" is removed so suggests that this step is clobbering parameters. But not sure...


Not sure whether the issue is with:



	
gerrit-trigger-plugin

	
rebuilder plugin

	
Jenkins core



but seems like a bug IMO.

3 attachments

- [downstream.xml](https://issues.jenkins.io/secure/attachment/31373/downstream.xml)
- [gerrit-trigger.xml](https://issues.jenkins.io/secure/attachment/31374/gerrit-trigger.xml)
- [upstream.xml](https://issues.jenkins.io/secure/attachment/31372/upstream.xml)

Start with downstream.xml, upstream.xml, and gerrit-trigger.xml, then reproduce the listed Gerrit event and use “Rebuild last” on the downstream job. Compare the parameters with and without “This build is parameterized,” and determine whether the loss belongs to the gerrit-trigger-plugin, rebuild-plugin, or Jenkins core. Done means the Gerrit build parameters are retained during rebuild.

Written by the indexing model from the issue text.