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

Disable shallow clone when we know a merge will take place

XMLWordPrintable

      There is an issue when building pull requests and the clone trait is present with shallow clone option.
      Apparently you need some history in order to be able to do a merge.

      We need to disable shallow clone when we know a merge will take place.

      At the first look, this can be fixed in
      com.cloudbees.jenkins.plugins.bitbucket.BitbucketGitSCMBuilder
      org.jenkinsci.plugins.github_branch_source.GitHubSCMBuilder

      I had identified the problem using bitbucket-branch-source-plugin but the should be visible on github-branch-source-plugin also..

          [JENKINS-45771] Disable shallow clone when we know a merge will take place

          Alexandru Pătrănescu created issue -
          Mark Waite made changes -
          Issue Type Original: Bug [ 1 ] New: New Feature [ 2 ]
          Mark Waite made changes -
          Assignee Original: Mark Waite [ markewaite ]
          Stephen Connolly made changes -
          Description Original: There is an issue when building pull requests and the clone trait is present with shallow clone option.
          Apparently you need some history in order to be able to do a merge.

          We need to disable shallow clone when we know a merge will take place.

          At the first look, this can be fixed in
          {{com.cloudbees.jenkins.plugins.bitbucket.BitbucketGitSCMBuilder}}
          {{org.jenkinsci.plugins.github_branch_source.GitHubSCMBuilder}}

          I had identified the problem using bitbucket-branch-source-plugin but the should be visible on github-branch-source-plugin also.
          		 New: There is an issue when building pull requests and the clone trait is present with shallow clone option.
           Apparently you need some history in order to be able to do a merge.

          We need to disable shallow clone when we know a merge will take place.

          At the first look, this can be fixed in
           {{com.cloudbees.jenkins.plugins.bitbucket.BitbucketGitSCMBuilder}}
           {{org.jenkinsci.plugins.github_branch_source.GitHubSCMBuilder}}

          I had identified the problem using bitbucket-branch-source-plugin but the should be visible on github-branch-source-plugin also..
          Stephen Connolly made changes -
          Remote Link New: This issue links to "git-client-plugin#255 (Web Link)" [ 17335 ]
          Stephen Connolly made changes -
          Remote Link New: This issue links to "git-plugin#516 (Web Link)" [ 17336 ]
          Stephen Connolly made changes -
          Assignee New: Stephen Connolly [ stephenconnolly ]
          Stephen Connolly made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          Stephen Connolly made changes -
          Remote Link New: This issue links to "gitea-plugin#4 (Web Link)" [ 17337 ]
          Stephen Connolly made changes -
          Remote Link New: This issue links to "bitbucket-branch-source-plugin#64 (Web Link)" [ 17338 ]
          Stephen Connolly made changes -
          Remote Link New: This issue links to "github-branch-source-plugin#150 (Web Link)" [ 17339 ]

            nfalco Nikolas Falco
            drealecs Alexandru Pătrănescu
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:
              Resolved: