[JIRA] (JENKINS-60412) Additional behavior "Discover open changes" not working for using Gerrit as SCM in Jenkins Shared Library configuration
Title: Message Title Luca Domenico Milanesio closed an issue as Fixed Considering this as fixed from v0.4.1 Jenkins / JENKINS-60412 Additional behavior "Discover open changes" not working for using Gerrit as SCM in Jenkins Shared Library configuration Change By: Luca Domenico Milanesio Status: Open Closed Resolution: Fixed Released As: 0.4.1 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60412) Additional behavior "Discover open changes" not working for using Gerrit as SCM in Jenkins Shared Library configuration
Title: Message Title Felipe Santos commented on JENKINS-60412 Re: Additional behavior "Discover open changes" not working for using Gerrit as SCM in Jenkins Shared Library configuration Checked, everything works fine without having to specify any Refspec, just by using the addiotional behavior "Discover open changes" 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.203469.1575926699000.2434.1578275940119%40Atlassian.JIRA.
[JIRA] (JENKINS-60412) Additional behavior "Discover open changes" not working for using Gerrit as SCM in Jenkins Shared Library configuration
Title: Message Title Luca Domenico Milanesio commented on JENKINS-60412 Re: Additional behavior "Discover open changes" not working for using Gerrit as SCM in Jenkins Shared Library configuration Felipe Santos can you check again now with v0.4.1? 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.203469.1575926699000.2280.1578247920122%40Atlassian.JIRA.
[JIRA] (JENKINS-60412) Additional behavior "Discover open changes" not working for using Gerrit as SCM in Jenkins Shared Library configuration
Title: Message Title Luca Domenico Milanesio commented on JENKINS-60412 Re: Additional behavior "Discover open changes" not working for using Gerrit as SCM in Jenkins Shared Library configuration I believe this was caused by the issue JENKINS-60364 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.203469.1575926699000.1022.1577717820108%40Atlassian.JIRA.
[JIRA] (JENKINS-60412) Additional behavior "Discover open changes" not working for using Gerrit as SCM in Jenkins Shared Library configuration
Title: Message Title Felipe Santos created an issue Jenkins / JENKINS-60412 Additional behavior "Discover open changes" not working for using Gerrit as SCM in Jenkins Shared Library configuration Issue Type: Bug Assignee: Luca Domenico Milanesio Components: gerrit-code-review-plugin Created: 2019-12-09 21:24 Environment: gerrit-code-review-plugin 0.3.7 Jenkins 2.190.3 Gerrit 2.14.20 Priority: Minor Reporter: Felipe Santos This plugin adds Gerrit as SCM. However, for using Gerrit as the SCM for configuring a Jenkins Shared Library, the additional behavior "Discover open changes" isn't working. How to replicate: Go to Manage Jenkins, click on Configure System. Scroll down to Global Pipeline Libraries. Configure everything as usual, select Gerrit for Source Code Management. You might take note that by default the Additional behavior "Discover open changes" comes. However, if you try to run a pipeline using a version of the library that is not merged yet (open change), Jenkins won't be able to fetch or locate that revision (the version is identified by the Git commit hash). Workaround: Since the option "Discover open changes doesn't work, you can delete it. On the additional behavior "Specify ref specs", add one and put the value: +refs/changes/:refs/changes/ Now, if you try to run a pipeline specifying a version not merged yet, Jenkins will be able to fetch it.
