Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-37658

Github-branch-source plugin should support git plugin extensions

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      Github branch source should support all the same extensions as the git client plugin ("Clean Before Checkout", "Clean After Checkout ", etc). it currently does not provide a way to add them, while other pipeline plugins do support them.

      See "Additional Behaviors" in the attached screenshot.

        Attachments

          Issue Links

            Activity

            Hide
            pshirshov P S added a comment -

            Related ticket: JENKINS-42947

            Show
            pshirshov P S added a comment - Related ticket:  JENKINS-42947
            Hide
            bitwiseman Liam Newman added a comment -

            Stephen Connolly
            Could you describe why you resolved this a duplicate? I can see that the linked issue has some overlap with this one, but it is not the same thing. This requests that the github branch plugin support the same open-ended set of extensions that the git plugin does. The linked issue implements a limited subset with a different UI.

            Show
            bitwiseman Liam Newman added a comment - Stephen Connolly Could you describe why you resolved this a duplicate? I can see that the linked issue has some overlap with this one, but it is not the same thing. This requests that the github branch plugin support the same open-ended set of extensions that the git plugin does. The linked issue implements a limited subset with a different UI.
            Hide
            stephenconnolly Stephen Connolly added a comment -

            Liam Newman All the extensions available on Git SCM Source are now available on GitHub and Bitbucket (except the ability to set the source code browser, because on GitHub and Bitbucket the only browser to set it to is GitHub / Bitbucket Respectively)

            There were a number of extensions on GitSCM that were exposed to GitSCMSource and should never have been. Those extensions have been removed from GitSCMSource and subclasses.

            The GitHub plugin now supports all the GitSCMExtensions that are relevant in the context of an SCMSource, hence duplicate

            Show
            stephenconnolly Stephen Connolly added a comment - Liam Newman All the extensions available on Git SCM Source are now available on GitHub and Bitbucket (except the ability to set the source code browser, because on GitHub and Bitbucket the only browser to set it to is GitHub / Bitbucket Respectively) There were a number of extensions on GitSCM that were exposed to GitSCMSource and should never have been . Those extensions have been removed from GitSCMSource and subclasses. The GitHub plugin now supports all the GitSCMExtensions that are relevant in the context of an SCMSource, hence duplicate
            Hide
            bitwiseman Liam Newman added a comment -

            Stephen Connolly
            Excellent! Thanks!

            Show
            bitwiseman Liam Newman added a comment - Stephen Connolly Excellent! Thanks!
            Hide
            lucasocio Leandro Lucarella added a comment -

            What about GitHub organizations? When I create an org there is no way to configure this via the config interface. After digging a lot I found https://support.cloudbees.com/hc/en-us/articles/226122247-How-to-Customize-Checkout-for-Pipeline-Multibranch- which helped to finally be able to do this in the Jenkinsfile, but still it's super complicated and you need to mess with permissions approval.

            Show
            lucasocio Leandro Lucarella added a comment - What about GitHub organizations? When I create an org there is no way to configure this via the config interface. After digging a lot I found https://support.cloudbees.com/hc/en-us/articles/226122247-How-to-Customize-Checkout-for-Pipeline-Multibranch- which helped to finally be able to do this in the Jenkinsfile, but still it's super complicated and you need to mess with permissions approval.

              People

              • Assignee:
                Unassigned
                Reporter:
                bitwiseman Liam Newman
              • Votes:
                44 Vote for this issue
                Watchers:
                43 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: