| Key: |
QB-201
|
| Type: |
Bug
|
| Status: |
Resolved
|
| Resolution: |
Cannot Reproduce
|
| Priority: |
Major
|
| Assignee: |
Robin Shen
|
| Reporter: |
Bryan Dyck
|
| Votes: |
0
|
| Watchers: |
1
|
|
If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 02/Feb/07 06:19 PM
Updated: 01/Mar/07 11:02 PM
|
|
| Component/s: |
None
|
| Affects Version/s: |
None
|
| Fix Version/s: |
None
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
Environment:
|
WinXP-64, Tomcat 5.5.17, JDK5, QuickBuild 1.2.2, Perforce 2006.1
|
|
|
I have recently started rolling out QuickBuild v1.2.2 to my build machines and noticed that configurations which have a "Label checked out code" step are no longer updating their associated Perforce labels.
In the build log output, the step shows as passing the necessary condition, executing and then completing, but the usual P4 labelspec output does not appear; also, the timestamps on the executing message and the completed message are exactly the same. The label step was working fine on QuickBuild v.1.1.4, and no changes in QuickBuild's behavior were observed during a Perforce server software upgrade a few weeks ago.
|
|
Description
|
I have recently started rolling out QuickBuild v1.2.2 to my build machines and noticed that configurations which have a "Label checked out code" step are no longer updating their associated Perforce labels.
In the build log output, the step shows as passing the necessary condition, executing and then completing, but the usual P4 labelspec output does not appear; also, the timestamps on the executing message and the completed message are exactly the same. The label step was working fine on QuickBuild v.1.1.4, and no changes in QuickBuild's behavior were observed during a Perforce server software upgrade a few weeks ago. |
Show » |
| There are no comments yet on this issue.
|
|
Perforce labels are not being updated in the "Label checked out code" step