L
L
LittleFatNinja2018-12-06 13:29:56
System administration
LittleFatNinja, 2018-12-06 13:29:56

Why does it stop running bydy on the crown?

An old situation ..
I have the "bitbuket pull request builder" plugin configured, and it * * * * *checks the status of pull requests every minute, everything works fine, it starts builds, BUT after a while (approximately after 5 hours) it just stops running builds.
That is, I create a pool of requests, but the builds on them are not executed.
You just need to restart jenkins. as everything immediately becomes normal, the work continues, BUT not for long, the problem repeats again.
Maybe someone came across?
OS - CentOS
Jenkins ver. 2.150.1
When the builds are working, the logs are something like this (pure vornings):

Dec 06, 2018 10:42:55 AM WARNING bitbucketpullrequestbuilder.bitbucketpullrequestbuilder.bitbucket.ApiClient send
Response status: HTTP/1.1 404 Not Found | URI: */commit/ee632a0974e1/statuses/build/jenkins-2ee78b7dbf552378670ff1d0b99978fc | Response body: {"type": "error", "error": {"message": "Build status with key 'jenkins-2ee78b7dbf552378670ff1d0b99978fc' for node ee632a0974e1878a96e4969ff69b29f187f484e3of repository * not found"}}

Dec 06, 2018 10:42:55 AM WARNING hudson.triggers.Trigger checkTriggers
bitbucketpullrequestbuilder.bitbucketpullrequestbuilder.BitbucketBuildTrigger.run() failed for [email protected][]
java.lang.NullPointerException
  at bitbucketpullrequestbuilder.bitbucketpullrequestbuilder.BitbucketRepository.addFutureBuildTasks(BitbucketRepository.java:122)
  at bitbucketpullrequestbuilder.bitbucketpullrequestbuilder.BitbucketPullRequestsBuilder.run(BitbucketPullRequestsBuilder.java:38)
  at bitbucketpullrequestbuilder.bitbucketpullrequestbuilder.BitbucketBuildTrigger.run(BitbucketBuildTrigger.java:292)
  at hudson.triggers.Trigger.checkTriggers(Trigger.java:278)
  at hudson.triggers.Trigger$Cron.doRun(Trigger.java:226)
  at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:72)
  at jenkins.security.ImpersonatingScheduledExecutorService$1.run(ImpersonatingScheduledExecutorService.java:58)
  at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
  at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
  at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
  at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
  at java.lang.Thread.run(Thread.java:748)

When builds stop running, nothing is written to the logs at all
5c0934df6d1aa516182605.png

Answer the question

In order to leave comments, you need to log in

2 answer(s)
S
ser_rostr2, 2018-12-28
@ser_rostr2

See if you have any other pull request plugins running? Specifically the Stash pullrequest builder plugin, try disabling them.

A
Ainur Valiev, 2018-12-08
@vaajnur

Every minute is too often. Set every 5

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question