[JIRA] (JENKINS-55071) Slow branch scan when using Bitbucket source
Title: Message Title Łukasz Wojciechowski commented on JENKINS-55071 Re: Slow branch scan when using Bitbucket source Joseph Petersen - can't agree with you. I still use what you referred, to limit Jenkins actions to only selected set of branches. But even then, Jenkins "blindly" asks Bitbucket API about all branches for given repository. Even worse, I believe it does only 10 rows per request (while it could ask for 100). Check my comment again, please. I am about places like this one: https://github.com/jenkinsci/bitbucket-branch-source-plugin/blob/master/src/main/java/com/cloudbees/jenkins/plugins/bitbucket/client/BitbucketCloudApiClient.java#L454 There is no code that modifies API calls for list of branches. In my case it takes 3-4 minutes between clicking on Build now and first Pipeline line being executed. This is why I needed a patch. Thanks! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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.196123.1544171467000.24028.1560045420217%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55071) Slow branch scan when using Bitbucket source
Title: Message Title Łukasz Wojciechowski commented on JENKINS-55071 Re: Slow branch scan when using Bitbucket source Not sure I'll bring anything to the topic but at least I can share my "solution" for the same problem. In my case, we have projects with crazy amount of branches backed by mercurial which results in 3+ minutes delays. In practice, we need Jenkins build kick in, only for a very small subset of branches so at some point I've ended up building my own version of bitbucket-branch-source-plugin. Note, that I have "zero" experience in Java dev world. So, with below change I got rid of that nasty delay before every build and in the end it was all I needed. https://github.com/lukaswoj/bitbucket-branch-source-plugin/commit/549899cf8d8b0229c37a3a155b588f36b98f2c78 This is how I build it, launched from repo root dir docker run -it -v "$(pwd)":/usr/src/mymaven -w /usr/src/mymaven maven:latest mvn -DskipTests package You should end up with HPI file generated under "target" subdirectory. HPI file can be installed under Upload Plugin section on "/pluginManager/advanced" page of your Jenkins installation. Hope this will be useful for someone. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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.
[JIRA] (JENKINS-41323) Do not throw exception during hash computation if source code is not available
Title: Message Title Łukasz Wojciechowski commented on JENKINS-41323 Re: Do not throw exception during hash computation if source code is not available Thanks Ulli Hafner for picking this up. I'm aware that those additional functionalities won't work as expected but this is IMO justified as long as core functionality (publishing the base report information) is there. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-33610) IOException with Clover 4.6 plugin
Title: Message Title Łukasz Wojciechowski commented on JENKINS-33610 Re: IOException with Clover 4.6 plugin Marek Parfianowicz - sorry but it looks like I lied in my previous comment. After I removed "Archiving Artifacts" - I still see the same exception being thrown. The difference, though is that it does no longer causes build to end up with FAILURE state - this is why I missed that fact. When my build turned from red to green I blindly assumed the exception is gone but apparently this is not the case. I would happily provide a stack trace but I need guidance on how to produce it. Not sure why in this case stack trace is missing. Within our Jenkins setup, other exceptions that occurs sometimes have full stack trace shown "by default". Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-41323) Make it possible to parse XML report without access to source code
Title: Message Title Łukasz Wojciechowski created an issue Jenkins / JENKINS-41323 Make it possible to parse XML report without access to source code Issue Type: Improvement Assignee: Ulli Hafner Components: dry-plugin Created: 2017/Jan/23 1:26 PM Priority: Minor Reporter: Łukasz Wojciechowski Hi there First of all - sorry if this is not the right way of asking such questions. I'm trying to migrate from freestyle PMD plugin based duplication report to pipelines DRY plugin based duplication report. In our build flow, we launch ant build that produces cpd-pmd XML report inside of a docker container. This docker image/container is the only place where source code lives. After XML is ready it is copied to a side and docker container is destroyed. On next pipeline step I'm trying to publish DRY report which fails with java.io.FileNotFoundException: /var/www/project/sourceFile.php (No such file or directory) I've traced this to below line in dry plugin source code: https://github.com/jenkinsci/dry-plugin/blob/dry-2.46/src/main/java/hudson/plugins/dry/parser/DuplicationParserRegistry.java#L91 I understand the reason why exception is thrown - plugin excepts/assumes that all the files mentioned in XML are available and it calculates some kind of hash for each (probably for diffing with previous runs reasons - just guessing). Since XML itself contains enough information to make the report itself - I would love to see an option that could be used to disable this part of code. Is it reasonable/possible to implement such improvement within dry plugin?
[JIRA] (JENKINS-33610) IOException with Clover 4.6 plugin
Title: Message Title Łukasz Wojciechowski commented on JENKINS-33610 Re: IOException with Clover 4.6 plugin Hi there, I was dealing with the same problem. I'm using latest, 4.7.1 version. Not sure how this is related but the error is gone after I removed "Archiving artifacts" step. And it did not matter if I had it before or after "Clover Publisher" step. I hope this will be helpful to anyone Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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.
