[JIRA] (JENKINS-49713) gerrit-plugin exposes change-requests as normal branches instead of pull-requests
Title: Message Title lucamilanesio updated JENKINS-49713 Jenkins / JENKINS-49713 gerrit-plugin exposes change-requests as normal branches instead of pull-requests Change By: lucamilanesio Status: In Review Closed Resolution: Fixed Released As: gerrit-code-review-0.2 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49713) gerrit-plugin exposes change-requests as normal branches instead of pull-requests
Title: Message Title lucamilanesio updated JENKINS-49713 Jenkins / JENKINS-49713 gerrit-plugin exposes change-requests as normal branches instead of pull-requests Change By: lucamilanesio Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49713) gerrit-plugin exposes change-requests as normal branches instead of pull-requests
Title: Message Title lucamilanesio commented on JENKINS-49713 Re: gerrit-plugin exposes change-requests as normal branches instead of pull-requests It was a bit tricky, but I've managed to introduce the new 'Changes' category: https://github.com/jenkinsci/gerrit-code-review-plugin/pull/18 More work will follow to make the branch name more "readable" Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49713) gerrit-plugin exposes change-requests as normal branches instead of pull-requests
Title: Message Title lucamilanesio updated an issue Jenkins / JENKINS-49713 gerrit-plugin exposes change-requests as normal branches instead of pull-requests Change By: lucamilanesio Comment: Duplicate of JENKINS-49897 ? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49713) gerrit-plugin exposes change-requests as normal branches instead of pull-requests
Title: Message Title lucamilanesio started work on JENKINS-49713 Change By: lucamilanesio Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49713) gerrit-plugin exposes change-requests as normal branches instead of pull-requests
Title: Message Title lucamilanesio commented on JENKINS-49713 Re: gerrit-plugin exposes change-requests as normal branches instead of pull-requests Duplicate of JENKINS-49897 ? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49713) gerrit-plugin exposes change-requests as normal branches instead of pull-requests
Title: Message Title Sorin Sbarnea updated an issue Jenkins / JENKINS-49713 gerrit-plugin exposes change-requests as normal branches instead of pull-requests Change By: Sorin Sbarnea It seems that when using gerrit-plugin in combination with multibranch-pipelines, we get all discovered branches as normal branches instead of having them split between real-branches and temporary ones (pull-requests).I am attaching screenshots of a sample github repository and a gerrit sample repository, so it is clearly visible that multibranch-pipeline does treat CRs as branches instead of PRs (they are not displayed in their separated tab).This is also likely to affect the Blue Ocean gui too and it may be a real deal for users that do have lots of production branches and open pull requests. I know for sure that having 5-10 production branches and 5-50 open CRs is not uncommon. Another issue spotted here is that the patchset version is included in the branch name, which is a real issue because it means that a Jenkins will create a new temporary branch for each updated changeset, instead of using a single one with multiple builds. Having the build history in one place is key as it allows users (and reviewers) to see how execution changed in time. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49713) gerrit-plugin exposes change-requests as normal branches instead of pull-requests
Title: Message Title Sorin Sbarnea created an issue Jenkins / JENKINS-49713 gerrit-plugin exposes change-requests as normal branches instead of pull-requests Issue Type: Bug Assignee: lucamilanesio Attachments: multibranch-github.png, mutibranch-gerrit.png Components: gerrit-plugin Created: 2018-02-23 10:24 Priority: Major Reporter: Sorin Sbarnea It seems that when using gerrit-plugin in combination with multibranch-pipelines, we get all discovered branches as normal branches instead of having them split between real-branches and temporary ones (pull-requests). I am attaching screenshots of a sample github repository and a gerrit sample repository, so it is clearly visible that multibranch-pipeline does treat CRs as branches instead of PRs (they are not displayed in their separated tab). This is also likely to affect the Blue Ocean gui too and it may be a real deal for users that do have lots of production branches and open pull requests. I know for sure that having 5-10 production branches and 5-50 open CRs is not uncommon.
