Hi,
I have a request to trigger QB configuration automatically after Gerrit "patch set" is created.
I see same request already created in: http://track.pmease.com/browse/QB-2358
Is there any solution for it?
Thanks!
Hi,
I have a request to trigger QB configuration automatically after Gerrit "patch set" is created.
I see same request already created in: http://track.pmease.com/browse/QB-2358
Is there any solution for it?
Thanks!
Thanks!
BTW - Found following configuration in demo server: "Build Against Gerrit Changes" (http://demo.pmease.com/overview/130) but it empty - not steps...
I guess this should implements what I need.
Are you plan to implements it?
For now, you may add a Gerrit repository in QB, and checkout the repository to do necessary things against it. Then schedule the configuration to run periodically. When scheduled time reaches, QB will trigger the build if there are new patch sets.
"Build Condition" was set to "If changes found in referenced repositories" and "Include/Exclude Path Patterns" was set to my gerrit repos.
However, when configuration starts run it create new builds for all open patch-sets.
In documentation - https://wiki.pmease.com/display/QB80/Build+Against+Specific+Gerrit+Change, describes a solution that user choose the the relevant changes in a prompt variable.
Is there a way to run it only on new patch-sets refer to previous build?
Hi Robin,
Is it possible to trigger the configuration only on new patch-set automatically- without user input?
Or, how can I know what are the new patch-set refer to previous run?
Thanks
You are right that QB will rebuild all open changes. This is because Gerrit does not provide a stable git ref pointing to latest commit of the change, so QB can not use current branch/ref monitoring mechanism to monitor ref changes. We need to introduce some other mechanism to solve this issue, and I filed an improvement request for this:
https://track.pmease.com/browse/QB-3426
QB9 already has the ability to only build open changes with new patch sets. Please refer to comments of QB-3426 for details: