[JIRA] (JENKINS-55038) `Parameterized Remote Trigger Plugin` sometimes fails with poll interval value more than 5 minutes
Title: Message Title Nick Korsakov commented on JENKINS-55038 Re: `Parameterized Remote Trigger Plugin` sometimes fails with poll interval value more than 5 minutes KaiHsiang Chang, thanks for fast code review. Can we close the issue? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.196080.1544027892000.3170.1585585140345%40Atlassian.JIRA.
[JIRA] (JENKINS-55038) `Parameterized Remote Trigger Plugin` sometimes fails with poll interval value more than 5 minutes
Title: Message Title Nick Korsakov edited a comment on JENKINS-55038 Re: `Parameterized Remote Trigger Plugin` sometimes fails with poll interval value more than 5 minutes Described problem is still reproduced reproducing , because plugin does not take into account state of the remote build, i.e. all `queued` items should be processed in time less than 5 minutes.[~cashlalala], please look at my pull request: [ https://github.com/jenkinsci/parameterized-remote-trigger-plugin/pull/65 ] Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.196080.1544027892000.8885.1584540660270%40Atlassian.JIRA.
[JIRA] (JENKINS-55038) `Parameterized Remote Trigger Plugin` sometimes fails with poll interval value more than 5 minutes
Title: Message Title Nick Korsakov reopened an issue Described problem still reproduced, because plugin does not take into account state of the remote build, i.e. all `queued` items should be processed in time less than 5 minutes. KaiHsiang Chang, please look at my pull request: https://github.com/jenkinsci/parameterized-remote-trigger-plugin/pull/65 Jenkins / JENKINS-55038 `Parameterized Remote Trigger Plugin` sometimes fails with poll interval value more than 5 minutes Change By: Nick Korsakov Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-55038) `Parameterized Remote Trigger Plugin` sometimes fails with poll interval value more than 5 minutes
Title: Message Title Nick Korsakov commented on JENKINS-55038 Re: `Parameterized Remote Trigger Plugin` sometimes fails with poll interval value more than 5 minutes KaiHsiang Chang thank you very much for your work. We will wait for the next plugin release. 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-55038) `Parameterized Remote Trigger Plugin` sometimes fails with poll interval value more than 5 minutes
Title: Message Title
Nick Korsakov updated an issue
Jenkins / JENKINS-55038
`Parameterized Remote Trigger Plugin` sometimes fails with poll interval value more than 5 minutes
Change By:
Nick Korsakov
There is a problem when we try to use poll interval parameter's value more than 300 seconds(5 minutes). We have a Jenkins pipeline which may take from 30 to 60 minutes.In some cases Jenkins `queued` item may move to the `pending` state as it described here:[https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/Queue.java#L139]In such case the plugin use user specified poll interval time out value to check queued item state:[https://github.com/jenkinsci/parameterized-remote-trigger-plugin/blob/master/src/main/java/org/jenkinsci/plugins/ParameterizedRemoteTrigger/RemoteBuildConfiguration.java#L696]But all `queued` items in the Jenkins have time to live only 5 minutes as you can see it here:[https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/Queue.java#L218]As result we have triggered `build` on the remote Jenkins server but failed build(`Max number of connection retries have been exeeded` error from the plugin) on the main Jenkins server: {code:java}Triggering parameterized remote job 'http://192.168.200.8:6680/job/RunTests' Using job-level defined 'Credentials Authentication' as user '***' (Credentials ID '***')Triggering remote job now.CSRF protection is enabled on the remote server.The remote job is pending. Waiting for next available executor on master. Remote job queue number: 124200Waiting for remote build to be executed...Waiting for 300 seconds until next poll.Connection to remote server failed [404], waiting for to retry - 300 seconds until next attempt. URL: http://192.168.200.8:6680//queue/item/124200/api/json/, parameters: Retry attempt #1 out of 5Connection to remote server failed [404], waiting for to retry - 300 seconds until next attempt. URL: http://192.168.200.8:6680//queue/item/124200/api/json/, parameters: Retry attempt #2 out of 5Connection to remote server failed [404], waiting for to retry - 300 seconds until next attempt. URL: http://192.168.200.8:6680//queue/item/124200/api/json/, parameters: Retry attempt #3 out of 5Connection to remote server failed [404], waiting for to retry - 300 seconds until next attempt. URL: http://192.168.200.8:6680//queue/item/124200/api/json/, parameters: Retry attempt #4 out of 5Connection to remote server failed [404], waiting for to retry - 300 seconds until next attempt. URL: http://192.168.200.8:6680//queue/item/124200/api/json/, parameters: Retry attempt #5 out of 5Max number of connection retries have been exeeded.{code} From my point of view there is a simple fix: use default value of the poll interval(10 seconds) to check `queued` item state. Because in the `pending` state the `queued` item is staying only for a few seconds: {code:java}int pollIntervalForQueuedItem = this.pollInterval;if (pollIntervalForQueuedItem > DEFAULT_POLLINTERVALL) { pollIntervalForQueuedItem =
[JIRA] (JENKINS-55038) `Parameterized Remote Trigger Plugin` sometimes fails with poll interval value more than 5 minutes
Title: Message Title Nick Korsakov created an issue Jenkins / JENKINS-55038 `Parameterized Remote Trigger Plugin` sometimes fails with poll interval value more than 5 minutes Issue Type: Bug Assignee: KaiHsiang Chang Components: parameterized-remote-trigger-plugin Created: 2018-12-05 16:38 Environment: Jenkins version - 2.89.4 (Ubuntu 16.04.5 LTS x64, openjdk version "1.8.0_151") Parameterized Remote Trigger Plugin version - 3.0.5 Priority: Major Reporter: Nick Korsakov There is a problem when we try to use poll interval parameter's value more than 300 seconds(5 minutes). We have a Jenkins pipeline which may take from 30 to 60 minutes. In some cases Jenkins `queued` item may move to the `pending` state as it described here: https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/Queue.java#L139 In such case the plugin use user specified poll interval time out value to check queued item state: https://github.com/jenkinsci/parameterized-remote-trigger-plugin/blob/master/src/main/java/org/jenkinsci/plugins/ParameterizedRemoteTrigger/RemoteBuildConfiguration.java#L696 But all `queued` items in the Jenkins have time to live only 5 minutes as you can see it here: https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/Queue.java#L218 As result we have triggered `build` on the remote Jenkins server but failed build(`Max number of connection retries have been exeeded` error from the plugin) on the main Jenkins server: Triggering parameterized remote job 'http://192.168.200.8:6680/job/RunTests' Using job-level defined 'Credentials
