<< Back to previous view |
[QB-2491] QB doesn't list SCM changes since previous build when sync to Perforce label
|
|
Status: | Closed |
Project: | QuickBuild |
Component/s: | None |
Affects Version/s: | 6.0.21 |
Fix Version/s: | None |
Type: | Bug | Priority: | Major |
Reporter: | Phong Trinh | Assigned To: | Robin Shen |
Resolution: | Won't Fix | Votes: | 0 |
Remaining Estimate: | Unknown | Time Spent: | Unknown |
Original Estimate: | Unknown |
Description |
It seems that there is an issue with QB when syncing to Perforce label. Our continuous integration build creates a label after each successful build, and nightly build sync to latest label and then build. There are source code changes since last build, however, QB doesn't list them. Please look into as your earliest chance.
Thanks, ptrinh |
Comments |
Comment by Robin Shen [ 30/Jul/15 12:00 AM ] |
Yes, this is a limitation as we can not get the corresponding change number reliably from a label to calculate the changes. |
Comment by Martin [ 24/Apr/17 02:47 PM ] |
Hi Robin,
could you please elaborate more about "cannot get the corresponding change number reliably"? Running this small one-liner is returning the corresponding changelist of a label: {code} p4 -ztag -F %Revision% label -o mylabel | cut -d "@" -f 2 {code} |
Comment by Robin Shen [ 24/Apr/17 11:21 PM ] |
I am not aware of this command, will investigate to see if it can be improved. |
Comment by Martin [ 25/Apr/17 07:54 AM ] |
That would be really awesome as we have to use currently this command as a workaround for labels. |
Comment by Robin Shen [ 22/Jan/18 06:35 AM ] |
Looks like Perforce label usually does not have a global revision information attached. The revision information is specified at file level. Without a global revision, it is meaningless to calculate changes between two labels.
Please reopen it if you have other ideas. |