Title: Message Title
Andreas Fritiofson commented on JENKINS-49897
Re: gerrit-plugin pr branch names are incorrectly name
I would also vote for having only the Change number field as the PR name. Having the Patchset number as part of the branch/PR makes Jenkins forget the history of the change. All PRs only get one build because Patchsets are seen as different PRs, so the statistics provided by plugins such as Warnings are meaningless. I don't really buy the motivation for the Patchset number quoted above; that it's needed to retrigger a build of a Patchset. If a newer Patchset is uploaded, it obsoletes all previous Patchsets of that Change. They cannot be submitted, so what is the point of building them at all? In fact in a comment to JENKINS-60301, it's even discussed to abort ongoing builds of older Patchsets when a new one is uploaded. Besides, since the job for the current Patchset is removed when a new is uploaded, you can't even retrigger a build.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.11.1520103505000.1605.1575558300719%40Atlassian.JIRA.