History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: QB-2274
Type: Improvement Improvement
Status: Open Open
Priority: Major Major
Assignee: Robin Shen
Reporter: ChangSeop LEE
Votes: 3
Watchers: 3

If you were logged in you would be able to see more operations.

High availability on long running builds

Created: 02/Jan/15 07:24 AM   Updated: 02/Aug/21 09:32 PM
Component/s: None
Affects Version/s: None
Fix Version/s: None

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown

 Description  « Hide
Storing information of not yet started builds and start them after master restarting is a great feature.
And I would like to request one more feature in case of master restarting.

Each steps are passed to a buildagent and execution result will be passed to master normally.
But if master is down while the buildagent trying to sent step execution result, the build will be failed.
And it will waste huge time if a build usually take long time and the master suddenly failed.

So it will be great buildagent keep trying to send step execution result to master if master is down and master restores the build if a step execution result is reported from buildagent.

Please check below link from jenkins for more information.

 All   Comments   Work Log   Change History      Sort Order:
Change by Robin Shen [29/Mar/18 11:08 PM]
Field Original Value New Value
Comment [ QB8
1. Not running builds will be picked up when QB server is shutdown gracefully (for upgrade or maintenance etc)
2. The disconnect tolerance setting of a step tells the agent how long to tolerate in case there is a network loss to QB server. ]

Change by Robin Shen [29/Mar/18 11:08 PM]
Comment [ QB8 is able to solve this issue partially with above two features ]