[JIRA] (JENKINS-60274) Unable to use plugin with private Bitbucket repositories
Title: Message Title John Lawlor edited a comment on JENKINS-60274 Re: Unable to use plugin with private Bitbucket repositories I am also seeing this problem on Bitbucket 6.8.0, Jenkins 2.190.2 and the latest version of the plugin 1.0.3 . 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.203264.1574715014000.7641.1574853421746%40Atlassian.JIRA.
[JIRA] (JENKINS-60274) Unable to use plugin with private Bitbucket repositories
Title: Message Title John Lawlor commented on JENKINS-60274 Re: Unable to use plugin with private Bitbucket repositories I am also seeing this problem on Bitbucket 6.8.0, Jenkins 2.190.2 and the latest version of the plugin 1.0.3 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.203264.1574715014000.7638.1574853121052%40Atlassian.JIRA.
[JIRA] (JENKINS-21559) Default GIT to run 'git clone' instead of 'git fetch'
Title: Message Title John Lawlor commented on JENKINS-21559 Re: Default GIT to run 'git clone' instead of 'git fetch' There are other use cases for 'git clone' other than what has been outlined. We clone onto VMs provisioned by Openstack, so they are always brand new. In this scenario there is no need for 'git fetch'. I find that the default options used by the git client are much slower than a standard clone for example: time /opt/openet/git/bin/git fetch --no-tags --progress ssh://g...@bitbucket.openet.com:7999/project/repo.git +refs/heads/*:refs/remotes/origin/* --depth=5 real 4m25.940s user 2m52.796s sys 1m23.799s If I do the same thing with a standard clone: time git clone ssh://g...@bitbucket.openet.com:7999/project/repo.git --depth 5 real 0m43.012s user 0m26.575s sys 0m12.050s This particular repo has 5000 branches, if you could even turn off the '--progress' option it would help matters. The way that the jenkins plugin has decided to do the fetch favours verbosity over performance. It's 10 times slower than a standard clone. I would prefer if it favoured performance. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
