Key: |
QB-665
|
Type: |
Bug
|
Status: |
Resolved
|
Resolution: |
Fixed
|
Priority: |
Major
|
Assignee: |
Unassigned
|
Reporter: |
Roger Perkins
|
Votes: |
0
|
Watchers: |
0
|
If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 08/Oct/10 01:43 PM
Updated: 11/Oct/10 11:27 AM
|
|
Component/s: |
None
|
Affects Version/s: |
3.0.10
|
Fix Version/s: |
3.0.11
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
I was just setting up a test proof build and noticed that both agents started the sync process on my local PC simultaneosuly which resulted in failure due to the 2nd sync trying to do the same work as the first and not being able to do the operations it wanted (such as deleting files).
Ideally the agents would need to co-ordinate between themselves for a single sync to occur, they all use the same repository and even checkout step now. The plan is to eventually scale this up to at least 6 agents building different configurations at the same time.
|
Description
|
I was just setting up a test proof build and noticed that both agents started the sync process on my local PC simultaneosuly which resulted in failure due to the 2nd sync trying to do the same work as the first and not being able to do the operations it wanted (such as deleting files).
Ideally the agents would need to co-ordinate between themselves for a single sync to occur, they all use the same repository and even checkout step now. The plan is to eventually scale this up to at least 6 agents building different configurations at the same time. |
Show » |
|
It might also be another thing I need to bug up, but when a sync is done locally on my PC to check for changes, I don't think it specifies a revision to sync against, where the other agents do sync to a specific revision that should be fixed by the snapshot taking code. Is this something that needs changing?