Details
Assignee
Barak KorrenBarak Korren(Deactivated)Reporter
Barak KorrenBarak Korren(Deactivated)Components
Priority
Medium
Details
Details
Assignee
Barak Korren
Barak Korren(Deactivated)Reporter
Barak Korren
Barak Korren(Deactivated)Components
Priority
Created September 7, 2017 at 7:07 AM
Updated June 11, 2018 at 6:22 AM
We have a certain scenario that repeats itself in our system:
Developer sends a patch
CI jobs start running
Developer send a new patch-set with a trivial change (e.g. commit message fix)
CI jobs complete and send results to Gerrit
Gerrit ignores the Jenkins vote because it was made on the older patch-set.
No vote is made by Jenkins on the new patch-set because it is configured to nor run jobs on trivial patches.
We've seen developers encounter this many times. I suspect this because even more frequent recently because PolyGerrit provides a UI for quickly editing commit messages.
We need to open tickets to the Gerrit developers and the Gerrit Trigger Plugin authors and see of they will be willing to help with this.