If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 02/Oct/15 01:13 AM
Updated: 18/Aug/20 10:39 PM
|
|
Component/s: |
None
|
Affects Version/s: |
6.0.21
|
Fix Version/s: |
None
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
File Attachments:
|
None
|
Image Attachments:
|
|
Environment:
|
Linux
|
|
Hi Support Team,
QuickBuild has an issue when syncing files from Perforce to QB workspace. Our continous integration build syncs to head of the change list, and it builds when changes found in the referenced repository. The issue is as the follow:
There was build which was synced to CL number 652498. Later there were several submissions into perforce branch, and their CL numbers were 652508, 652520, 652530, and 652536. Then the build was triggered and it synced to CL 652536, since this CL was the head CL at this point of time. Looks like QB didn't sync the updated files in CL 652508 and CL 652520 down to the workspace, since QB didn't list them in the SCM changes. I attached the screenshots of these builds and Perforce Change lists for your references.
Thanks,
ptrinh
|
Description
|
Hi Support Team,
QuickBuild has an issue when syncing files from Perforce to QB workspace. Our continous integration build syncs to head of the change list, and it builds when changes found in the referenced repository. The issue is as the follow:
There was build which was synced to CL number 652498. Later there were several submissions into perforce branch, and their CL numbers were 652508, 652520, 652530, and 652536. Then the build was triggered and it synced to CL 652536, since this CL was the head CL at this point of time. Looks like QB didn't sync the updated files in CL 652508 and CL 652520 down to the workspace, since QB didn't list them in the SCM changes. I attached the screenshots of these builds and Perforce Change lists for your references.
Thanks,
ptrinh |
Show » |
|
${repositories.get("your repo name").revision}