If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 08/Oct/10 03:47 PM
Updated: 27/Dec/12 02:39 PM
|
|
Component/s: |
None
|
Affects Version/s: |
3.0.10
|
Fix Version/s: |
4.0.89
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
Environment:
|
Operating System Windows 2003 5.2, x86
JVM Java HotSpot(TM) Client VM 11.3-b02, Sun Microsystems Inc.
QuickBuild Version 3.0.10 - Tue Oct 05 17:03:37 MSD 2010
Operating System Windows 2003 5.2, x86
JVM Java HotSpot(TM) Client VM 11.3-b02, Sun Microsystems Inc.
QuickBuild Version 3.0.10 - Tue Oct 05 17:03:37 MSD 2010
|
|
If mail server becomes inaccessible and QB sends an email-notification (for failed build in my case) this notification hangs in a queue and does not allow further build requests which are waiting for notification request completion but it seems there is no timeout for e-mail sending
I see following in config dashboard (2 hours passed by):
Requested By Schedule Date Priority Process Status Build Version
Scheduler 2010-10-08 17:45:11 5 SENDING_BUILD_NOTIFICATIONS 2.6.39.1390
Of course corporate e-mail server must be accessible but sometimes it is not and QB must not be dependable of such a thing, I guess
|
Description
|
If mail server becomes inaccessible and QB sends an email-notification (for failed build in my case) this notification hangs in a queue and does not allow further build requests which are waiting for notification request completion but it seems there is no timeout for e-mail sending
I see following in config dashboard (2 hours passed by):
Requested By Schedule Date Priority Process Status Build Version
Scheduler 2010-10-08 17:45:11 5 SENDING_BUILD_NOTIFICATIONS 2.6.39.1390
Of course corporate e-mail server must be accessible but sometimes it is not and QB must not be dependable of such a thing, I guess |
Show » |
|