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

Key: QB-2491
Type: Bug Bug
Status: Closed Closed
Resolution: Won't Fix
Priority: Major Major
Assignee: Robin Shen
Reporter: Phong Trinh
Votes: 0
Watchers: 0
Operations

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

QB doesn't list SCM changes since previous build when sync to Perforce label

Created: 29/Jul/15 08:09 PM   Updated: 22/Jan/18 06:35 AM
Component/s: None
Affects Version/s: 6.0.21
Fix Version/s: None

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


 Description  « Hide
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

 All   Comments   Work Log   Change History      Sort Order:
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.

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}

Robin Shen [24/Apr/17 11:21 PM]
I am not aware of this command, will investigate to see if it can be improved.

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.

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.