[JIRA] [core] (JENKINS-33491) Quiet Period does not refresh for subsequent builds

[m...@latiolais.net (JIRA)]

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

[m...@latiolais.net (JIRA)]

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]