[JIRA] [core] (JENKINS-33491) Quiet Period does not refresh for subsequent builds
Title: Message Title Daniel Beck commented on JENKINS-33491 Re: Quiet Period does not refresh for subsequent builds No. I've been busy with the release of Jenkins 2.0 and a large scale overhaul of our infrastructure this week, so this is far from the top of my priority list. That said, I'd be happy to review a pull request that fixes this. However, please note that a simple revert of the change in 1.618 will again break JENKINS-2180 , which, based on votes and watchers, is considered far more relevant than your use case, so that's not a feasible approach. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-33491) Quiet Period does not refresh for subsequent builds
Title: Message Title Łukasz Chełmicki commented on JENKINS-33491 Re: Quiet Period does not refresh for subsequent builds Any update to this bug? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-33491) Quiet Period does not refresh for subsequent builds
Title: Message Title Daniel Beck commented on JENKINS-33491 Re: Quiet Period does not refresh for subsequent builds Will investigate. IIRC last two paragraphs don't work as described, which is why I changed the behavior to begin with. If it's possible to address that part while restoring the previous quiet period behavior, I'll do so. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-33491) Quiet Period does not refresh for subsequent builds
Title: Message Title Daniel Beck assigned an issue to Daniel Beck Jenkins / JENKINS-33491 Quiet Period does not refresh for subsequent builds Change By: Daniel Beck Assignee: Daniel Beck Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-33491) Quiet Period does not refresh for subsequent builds
Title: Message Title Łukasz Chełmicki commented on JENKINS-33491 Re: Quiet Period does not refresh for subsequent builds In version 1.617 this feature was working fine. I even found the original description of this feature (https://jenkins.io/blog/2010/08/11/quiet-period-feature/) and current implementation changes fundaments of it. You mentioned that polling is resetting this timer, then bug is in implementation of polling mechanism if no changes in repo resets timer (no changes = no trigger = no timer reset) or people are incorrectly setting the quiet period value. Please give us back correct/previous implementation of this feature. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-33491) Quiet Period does not refresh for subsequent builds
Title: Message Title Daniel Beck commented on JENKINS-33491 Re: Quiet Period does not refresh for subsequent builds No. Cancel the queue item through the queue API if you want it gone. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-33491) Quiet Period does not refresh for subsequent builds
Title: Message Title Michael Latiolais reopened an issue This doesn't seem right. We use this feature together with Trigger builds remotely using an authentication token. This seems to completely undermine the function of a quiet period. Is there a way to force the timer to refresh? Jenkins / JENKINS-33491 Quiet Period does not refresh for subsequent builds Change By: Michael Latiolais Resolution: Not A Defect Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-33491) Quiet Period does not refresh for subsequent builds
Title: Message Title Daniel Beck resolved as Not A Defect This is deliberate to prevent items from being left waiting in the queue forever, which can happen e.g. when the polling interval is shorter than the waiting time. Jenkins / JENKINS-33491 Quiet Period does not refresh for subsequent builds Change By: Daniel Beck Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-33491) Quiet Period does not refresh for subsequent builds
Title: Message Title Michael Latiolais created an issue Jenkins / JENKINS-33491 Quiet Period does not refresh for subsequent builds Issue Type: Bug Assignee: Unassigned Components: core Created: 11/Mar/16 11:50 PM Environment: Jenkins ver. 1.642.1 Priority: Minor Reporter: Michael Latiolais We use wget to trigger builds from an external trigger. We have a 20 minute quiet time set on this project. When the first wget is called, it triggers the job and starts the quiet period timer. However, subsequent identical calls will not reset the timer. It continues to count down from the first call. Here are the calls I see in the log: -bash-4.1$ wget -v --delete-after 'http://SERVERNAME/buildByToken/build?job=BUILD_NAME=TOKEN_NAME' - 2016-03-11 15:29:39 - http://SERVERNAME/buildByToken/build?job=BUILD_NAME=TOKEN_NAME Resolving SERVERNAME... IP Connecting to SERVERNAME|IP|:80... connected. HTTP request sent, awaiting response... 201 Created Length: 0 [text/plain] Saving to: "build?job=BUILD_NAME=TOKEN_NAME" [ <=> ] 0 --.-K/s in 0s 2016-03-11 15:29:39 (0.00 B/s) - "build?job=BUILD_NAME=TOKEN_NAME" saved [0/0]
