jimsearle schrieb am Freitag, 4. März 2022 um 21:41:56 UTC+1:
> Hi, > > We have been longtime Jenkins user and recently started the transition to > Gerrit. > > The Jenkins Gerrit trigger kicks off the job for each commit that is in > the publish, but we would prefer just to run the job on the last changeset > which includes all the commits. This seems like it would be a common thing > and available in the configuration somewhere but I can't find anything. > > Your terminology is a bit unclear, so I'll try to translate it to typical gerrit terms: In gerrit you have changes (also called changesets) that are a single commit. So running a job for each commit is normal (in the gerrit world). => this is trigger 'patchset-created' Note that updates to such a change are done by amending the local commit, not by adding another commit in series and then pushing again to gerrit. This gives a new patchset on the change. A change in gerrit is fundamtentally different from a pull request in the github/gitlab world. Once all votes are in placesuch a commit can get "submitted" => merged to it's branch. ==> trigger: change-merged So I would say gerrit trigger behaves as expected... Björn > I can describe in more detail if this description is not clear. > > Thanks, > Jim > > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/165caaac-88ca-4b02-a5a1-ff17d5688d58n%40googlegroups.com.
