Hi. Our build server running Final Builder Server is in Melbourne, and our perforce server is in Brisbane, so since daylight savings time started last weekend the FBServer machine has been in a time zone one hour ahead of the perforce server.
This appears to have confused the Perforce trigger I have set up on the build machine. Once a triggered build runs, the machine ignores any new submits to Perforce for the next hour. For example, today we had the following commits in the relevant repository path in Perforce, and I'll indicate which ones triggered the trigger and caused FB Server to actuall run the build:
| Revision | Time submitted | Built by FBServer |
|---|---|---|
| 268191 | 9:30:19 AM | Yes, at 9:31:28 AM |
| 268192 | 9:31:55 AM | No |
| 268211 | 10:07:47 AM | No |
| 268213 | 10:09:53 AM | No |
| 268229 | 10:36:53 AM | Yes, at 10:38:04 AM |
| 268235 | 10:47:32 AM | No |
| 268340 | 11:52:09 AM | Yes, at 11:53:22 AM |
| 268342 | 11:52:50 AM | No |
| 268362 | 12:09:52 PM | No |
| 268430 | 12:54:17 PM | Yes, at 12:55:22 PM |
| 268433 | 12:56:46 PM | No |
| 268436 | 12:58:01 PM | No |
| 268485 | 1:17:08 PM | No |
| 268495 | 1:22:41 PM | No |
| 268496 | 1:24:23 PM | No |
The trigger/project is set up to Append to the queue, and normally ran for every commit to perforce prior to this week.