[JIRA] (JENKINS-50582) Limit amount of requests sent to BitBucket API
Title: Message Title Benjamin Fuchs edited a comment on JENKINS-50582 Re: Limit amount of requests sent to BitBucket API We are having the same issue, but with the BitbucketServerAPIClient.javaWe also would like to have an option to specify the maximum number of branches to consider, since it takes a long time to scan all branches in our case (also 5+ minutes).Currently I would start using this workaround: https://github.com/benjaminfuchs/bitbucket-branch-source-plugin/commit/ 79e63c5d360a61cd653543730bd5b7f72422a0ac fa41e9ba0af15e8c703e164cb5b9976e2a67e267 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50582) Limit amount of requests sent to BitBucket API
Title: Message Title Benjamin Fuchs edited a comment on JENKINS-50582 Re: Limit amount of requests sent to BitBucket API We are having the same issue, but with the BitbucketServerAPIClient.javaWe also would like to have an option to specify the maximum number of branches to consider, since it takes a long time to scan all open branches in our case (also 5+ minutes).Currently I would start using this workaround: https://github.com/benjaminfuchs/bitbucket-branch-source-plugin/commit/79e63c5d360a61cd653543730bd5b7f72422a0ac Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50582) Limit amount of requests sent to BitBucket API
Title: Message Title Benjamin Fuchs edited a comment on JENKINS-50582 Re: Limit amount of requests sent to BitBucket API We are having the same issue, but with the BitbucketServerAPIClient.javaWe also would like to have an option to specify the maximum number of branches to consider, since it takes a long time to scan all open branches in our case (also 5+ minutes). Currently I would start using this workaround: https://github.com/benjaminfuchs/bitbucket-branch-source-plugin/commit/79e63c5d360a61cd653543730bd5b7f72422a0ac Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50582) Limit amount of requests sent to BitBucket API
Title: Message Title Benjamin Fuchs commented on JENKINS-50582 Re: Limit amount of requests sent to BitBucket API We are having the same issue, but with the BitbucketServerAPIClient.java We also would like to have an option to specify the maximum number of branches to consider, since it takes a long time to scan all open branches in our case (also 5+ minutes). Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50582) Limit amount of requests sent to BitBucket API
Title: Message Title Łukasz Wojciechowski updated an issue Jenkins / JENKINS-50582 Limit amount of requests sent to BitBucket API Change By: Łukasz Wojciechowski Hi all,Company I work for uses Bitbucket + Mercurial repositories.Couple of repositories are really old and accumulated massive amount of branches.For some time already we observe longer and longer delays between Bitbucket commit webhook dispatch and the moment Jenkins starts to execute first line of our Pipeline.Delay in our case is from 5 to even 10 minutes which is very painful.After some digging and playing around I managed to build custom version of plugin that tries to fix this problem. [ https://github.com/jenkinsci/bitbucket-branch-source-plugin/compare/master...lukaswoj:master ] I believe that following above changes in scope of *pagelen* parameter being set to 100 (current maximum for which Bitbucket allows) would be a simple fix and at the same time it should make a lot of users happy. Those changes shortened ~5 minutes to "just" 30 seconds. Sorry for this contribution not being as it should, this was my first time ever working with Java code, Maven and locally launched Jenkins. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50582) Limit amount of requests sent to BitBucket API
Title: Message Title Łukasz Wojciechowski created an issue Jenkins / JENKINS-50582 Limit amount of requests sent to BitBucket API Issue Type: Improvement Assignee: Unassigned Components: bitbucket-branch-source-plugin Created: 2018-04-05 02:35 Priority: Trivial Reporter: Łukasz Wojciechowski Hi all, Company I work for uses Bitbucket + Mercurial repositories. Couple of repositories are really old and accumulated massive amount of branches. For some time already we observe longer and longer delays between Bitbucket commit webhook dispatch and the moment Jenkins starts to execute first line of our Pipeline. Delay in our case is from 5 to even 10 minutes which is very painful. After some digging and playing around I managed to build custom version of plugin that tries to fix this problem. https://github.com/jenkinsci/bitbucket-branch-source-plugin/compare/master...lukaswoj:master I believe that following above changes in scope of pagelen parameter being set to 100 (current maximum for which Bitbucket allows) would be a simple fix and at the same time it should make a lot of users happy. Sorry for this contribution not being as it should, this was my first time ever working with Java code, Maven and locally launched Jenkins.
