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

Github-branch-source plugin should support git plugin extensions

    XMLWordPrintable

Details

    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

          depends on

          New Feature - A new feature of the product, which has yet to be developed. JENKINS-31924 GitSCMSource should offer extensions

          • Major - Major loss of function.
          • Closed
          duplicates

          New Feature - A new feature of the product, which has yet to be developed. JENKINS-43507 Allow SCMSource and SCMNavigator subtypes to share common traits

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved
          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-36849 Github organization folder plugin fetch timeouts

          • Major - Major loss of function.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-37817 checkout scm should be able to override extensions/settings

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-37659 Github-organization-folder-plugin should support git client extensions

          • Major - Major loss of function.
          • Closed
          is related to

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-42351 Shallow clone on master when running job across slaves

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-34752 Changes screens don't provide links to GitHub Enterprise screens

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-37817 checkout scm should be able to override extensions/settings

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

          New Feature - A new feature of the product, which has yet to be developed. JENKINS-39750 scm should allow configuration in the Jenkinsfile

          • Major - Major loss of function.
          • Resolved

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-42860 RejectedAccessException: Scripts not permitted to use method hudson.plugins.git.GitSCM getBranches

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-42947 Bitbucket-branch-source plugin does not support GIT submodules

          • Major - Major loss of function.
          • Resolved
          links to

          Web Link CloudBees Internal CD-119

          Web Link discussion

          Web Link Workaround described on CloudBees website

          Activity

            Ascending order - Click to sort in descending order
            View 10 older comments
            pshirshov P S added a comment -

            Related ticket: JENKINS-42947

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

            stephenconnolly
            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.

            bitwiseman Liam Newman added a comment - stephenconnolly 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.
            stephenconnolly Stephen Connolly added a comment -

            bitwiseman 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

            stephenconnolly Stephen Connolly added a comment - bitwiseman 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
            bitwiseman Liam Newman added a comment -

            stephenconnolly
            Excellent! Thanks!

            bitwiseman Liam Newman added a comment - stephenconnolly Excellent! Thanks!
            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.

            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

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

              Dates

                Created:
                Updated:
                Resolved: