search

nishio-dens / bitbucket-pullrequest-builder-plugin

Bitbucket Pull Request Builder Plugin for Jenkins
Other
125 stars 145 forks source link

Pligin takes long time to kick the jenkins job #200

Closed chris248570 closed 5 years ago

chris248570 commented 5 years ago

I tried in different Jenkins and using 1.30.0 plugin.. Always plugin is taking too long to kick my Jenkins build job??... Is an issue or it's happening only for me..

CodeMonk commented 5 years ago

Welp, I'm not sure if anyone can help answer your question, since you're missing a couple of minor details.

  1. How slow is it? 1 second? 1 minute? 1 hour? 1 day? 1 year?
  2. Since 'kick' is a bit ambiguous, how, EXACTLY, are you kicking off your Jenkins build job?

Perhaps if we know what you are doing, and how long it is taking, we can actually comment on whether or not your experience is an issue, or it's happening only for you.

-Dave

chris248570 commented 5 years ago

@CodeMonk thanks for checking my issue.. My Jenkins jobs are taking time delay up to 30 to 40 min after my Pullrequest created/updated.. and sometimes if PullRequest is updated it's not even triggering the Jenkins job.. We do 3 times a day but now to test this issue we spin up other Jenkins and created Jenkins job and try to reproduce it and getting same issue , tried to update my Pullrequest every 30 min no luck. Is there anything I and doing wrong or it's happening with this plugin version 1.4.30 And I am seeing Rate limit is exceed

in the Jenkins system logs... Fetch PullRequests. Response status: HTTP/1.1 429 Unknown Status Code URI: https://bitbucket.org/api/..../pullrequests/?pagelen=50 Rate limit for this resource has been exceeded

CodeMonk commented 5 years ago

Yup -- there you have it. Atlassian throttles -- a LOT.

Cheers!

On Tue, Apr 30, 2019 at 12:43 PM chris248570 notifications@github.com wrote:

@CodeMonk https://github.com/CodeMonk thanks for checking my issue.. My Jenkins jobs are taking time delay up to 30 to 40 min after my Pullrequest created/updated.. and sometimes if PullRequest is updated it's not even triggering the Jenkins job.. And I am seeing Rate limit is exceeded in the Jenkins system logs... Fetch PullRequests. Response status: HTTP/1.1 429 Unknown Status Code URI: https://bitbucket.org/api/..../pullrequests/?pagelen=50 Rate limit for this resource has been exceeded

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/nishio-dens/bitbucket-pullrequest-builder-plugin/issues/200#issuecomment-488068464, or mute the thread https://github.com/notifications/unsubscribe-auth/AAA72VSZVXGEYJRHRMQTGMDPTCHOBANCNFSM4HJOLWUQ .

chris248570 commented 5 years ago

@CodeMonk any thoughts why my jobs are getting delays.. anything in your mind related to this error???

CodeMonk commented 5 years ago

Yes. When the code tries to look for new pull requests, the request fails, because it's being throttled by atlassian.

Eventually it will succeed.

If the period of time between the throttling and eventual success is non zero, then that total cumulative period will be delay in kicking off the build.

Once atlassian STARTS throttling, the throttling is generally pretty severe, so, that delay could get quite large.

There are some feature tickets here on moving to a triggered vs polling system, but, no one has contributed code, and I've been swamped lately :(

-Dave

chris248570 commented 5 years ago

Thanks @CodeMonk . Is there any alternate way to fix this issue right now by changing any settings or config before the new version or new code fix??..

CodeMonk commented 5 years ago

Don't hit bitbucket's api so hard. If you are using other plugins, try to be nice with them.

For this plugin, change the cron line to not poll as often. Hopefully that will reduce the throttling.

reddydheeraj commented 5 years ago

hello @CodeMonk is there any possibility in kicking off the PR build in Jenkins based off the "Webhook to Jenkins for Bitbucket Server" plugin in Bitbucket.. image

If this is possible .. presuming this would avoid polling to Bitbucket and kicks off the PR build without any delays. Also last but not least we've restrictions on polling to Bitbucket in our organization. Its a major stumbling block for us to get this amazing plugin into our workplace.

I'm very enthusiastic to know possibilities of avoiding polling (cron) and kickoff the PR build as soon as PR is opened with "Bitbucket Pull Requests Plugin"

CodeMonk commented 5 years ago

It is definitely possible -- that's what bbprb does. However, at this time, this plugin does not support it.

-Dave

On Fri, Jun 28, 2019 at 11:30 AM reddydheeraj notifications@github.com wrote:

hello @CodeMonk https://github.com/CodeMonk is there any possibility in kicking off the PR build in Jenkins based off the "Webhook to Jenkins for Bitbucket Server" plugin in Bitbucket.. [image: image] https://user-images.githubusercontent.com/51835172/60359295-aac26c00-99a6-11e9-9aa1-f37c16b037e2.png

If this is possible .. presuming this would avoid polling to Bitbucket and kicks off the PR build without any delays. Also last but not least we've restrictions on polling to Bitbucket in our organization. Its a major stumbling block for us to get this amazing plugin into our workplace.

I'm very enthusiastic to know possibilities of avoiding polling (cron) and kickoff the PR build as soon as PR is opened with "Bitbucket Pull Requests Plugin"

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/nishio-dens/bitbucket-pullrequest-builder-plugin/issues/200?email_source=notifications&email_token=AAA72VRBTBINZ2H2DJ4HSTDP4ZDDLA5CNFSM4HJOLWU2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODY2WKZA#issuecomment-506815844, or mute the thread https://github.com/notifications/unsubscribe-auth/AAA72VX5L747QE52IOG5IO3P4ZDDLANCNFSM4HJOLWUQ .