-
Bug
-
Resolution: Unresolved
-
Blocker
-
None
-
Jenkins 2.7
stash-pullrequest-builder-plugin 1.7
The cron based jobs are working fine until stash-pullrequest-builder-plugin is installed and configured for one of our gating job. The frequency to run is every 2 min. Since then all the cron based jobs are not triggered at specified time, but rather at random time. They also get triggered every time Stash is unavailable, such as during its backup. Hence all cron based jobs failed.
- links to
[JENKINS-41336] Cron based jobs are triggered at random times and also at the time Stash is unavailable
That's jenkins design - all Triggers inherit cron functionality, but it can be simply skipped.
Vivian zhang
added a comment - What I meant was this plugin should rely on Stash's post-commit webhook plugin for sending change notification to Jenkins, and trigger the build with poll scm option checked (no cron needed here). Looks like this place is to report Jenkins core bug, maybe I should file an issue report at the plugin's github site?
Vivian zhang
added a comment - What I meant was this plugin should rely on Stash's post-commit webhook plugin for sending change notification to Jenkins, and trigger the build with poll scm option checked (no cron needed here). Looks like this place is to report Jenkins core bug, maybe I should file an issue report at the plugin's github site? Vivian zhang
added a comment - That's how it's been working without this plugin, although I still like some of the features provided by this plugin.
Vivian zhang
added a comment - That's how it's been working without this plugin, although I still like some of the features provided by this plugin. 
Larry Brigman
added a comment - I'm seeing jobs queue when I get this error:
Mar 23, 2017 4:43:00 PM stashpullrequestbuilder.stashpullrequestbuilder.StashRepository getTargetPullRequests
INFO: Fetch PullRequests (ansible-checks).
java.util.concurrent.ExecutionException: java.net.SocketTimeoutException: Read timed out
at java.util.concurrent.FutureTask.report(FutureTask.java:122)
at java.util.concurrent.FutureTask.get(FutureTask.java:202)
at stashpullrequestbuilder.stashpullrequestbuilder.stash.StashApiClient.getRequest(StashApiClient.java:254)
at stashpullrequestbuilder.stashpullrequestbuilder.stash.StashApiClient.getPullRequests(StashApiClient.java:86)
Using Jenkins 2.44 on Ubuntu 14.04 LTS
OpenJDK 64bit Java 1.7.0_79
Stash Pull Request Builder 1.7
Against Stash/Bitbucket v4.4.1
The timeout is due to an issue on the bitbucket end but it shouldn't be causing a build to be queued.
Larry Brigman
added a comment - I'm seeing jobs queue when I get this error:
Mar 23, 2017 4:43:00 PM stashpullrequestbuilder.stashpullrequestbuilder.StashRepository getTargetPullRequests
INFO: Fetch PullRequests (ansible-checks).
java.util.concurrent.ExecutionException: java.net.SocketTimeoutException: Read timed out
at java.util.concurrent.FutureTask.report(FutureTask.java:122)
at java.util.concurrent.FutureTask.get(FutureTask.java:202)
at stashpullrequestbuilder.stashpullrequestbuilder.stash.StashApiClient.getRequest(StashApiClient.java:254)
at stashpullrequestbuilder.stashpullrequestbuilder.stash.StashApiClient.getPullRequests(StashApiClient.java:86)
Using Jenkins 2.44 on Ubuntu 14.04 LTS
OpenJDK 64bit Java 1.7.0_79
Stash Pull Request Builder 1.7
Against Stash/Bitbucket v4.4.1
The timeout is due to an issue on the bitbucket end but it shouldn't be causing a build to be queued. 
ivan palanevich
added a comment - You can try to use that fix -
https://github.com/kmoco2am/stash-pullrequest-builder-plugin/commit/da4ed53fb8f38f10df956175e7feda76f64f766e 
Jakub Bochenski
added a comment - So the issue here is that StashBuildTrigger.run runs for too long?
Jakub Bochenski
added a comment - So the issue here is that StashBuildTrigger.run runs for too long? Jakub Bochenski
added a comment - This issue has been closed because of inactivity. Please reopen it if you think it's still valid
Jakub Bochenski
added a comment - This issue has been closed because of inactivity. Please reopen it if you think it's still valid 
Luis Ehlen
added a comment - I just updated to the latest Jenkins LTS 2.204.2 and the latest version of the stash pull request builder plugin 1,17 (from 1.8) and the mentioned behavior with the cron based jobs appeared.
I can see this on my logs:
Feb 19, 2020 12:25:29 PM WARNING hudson.triggers.Trigger checkTriggersTrigger
stashpullrequestbuilder.stashpullrequestbuilder.StashBuildTrigger.run() triggered by hudson.maven.MavenModuleSet@45177041[JOB_NAME] spent too much time (54 sec) in its execution, other timers can be affected
Luis Ehlen
added a comment - I just updated to the latest Jenkins LTS 2.204.2 and the latest version of the stash pull request builder plugin 1,17 (from 1.8) and the mentioned behavior with the cron based jobs appeared.
I can see this on my logs:
Feb 19, 2020 12:25:29 PM WARNING hudson.triggers.Trigger checkTriggers Trigger
stashpullrequestbuilder.stashpullrequestbuilder.StashBuildTrigger.run() triggered by hudson.maven.MavenModuleSet@45177041 [JOB_NAME] spent too much time (54 sec) in its execution, other timers can be affected 
I'm surprised that the plugin requires cron to be set up for the job, which is very inefficient to go through all the open PRs every time. It should try to use the branch info provided by Stash post-commit hook instead.