Key: |
QB-2254
|
Type: |
Bug
|
Status: |
Resolved
|
Resolution: |
Fixed
|
Priority: |
Major
|
Assignee: |
Unassigned
|
Reporter: |
Daniel Yankowsky
|
Votes: |
0
|
Watchers: |
0
|
If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 03/Dec/14 09:14 PM
Updated: 05/Dec/14 02:42 AM
|
|
Component/s: |
None
|
Affects Version/s: |
5.1.36
|
Fix Version/s: |
5.1.40
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
Perforce had introduced an enhancement to their streams infrastructure called "task streams" a few versions ago. Task streams are like development streams, except that they branch files in a more lightweight fashion. Unfortunately, in doing this, they also made some commands sensitive to the "current workspace" (AKA "current client"). In particular, `p4 changes` now reports different results depending on the current client - if you don't specify a client, it will omit some results.
Since we're a paying customer, we have access to the source code. It looks like PerforceRepository.java, `getChangesBetween()` constructs the command-line used to look for changes, but does not include the `-c clientname` parameter that other commands do include. Fortunately, it looks like `setupClient()` has already been called, so it should be possible to pass the client name to `p4 changes`.
Specifically, I think this:
.addArgLine("changes -s submitted")
should look more like this:
.addArgLine("-c " + getClientName() + " changes -s submitted")
|
Description
|
Perforce had introduced an enhancement to their streams infrastructure called "task streams" a few versions ago. Task streams are like development streams, except that they branch files in a more lightweight fashion. Unfortunately, in doing this, they also made some commands sensitive to the "current workspace" (AKA "current client"). In particular, `p4 changes` now reports different results depending on the current client - if you don't specify a client, it will omit some results.
Since we're a paying customer, we have access to the source code. It looks like PerforceRepository.java, `getChangesBetween()` constructs the command-line used to look for changes, but does not include the `-c clientname` parameter that other commands do include. Fortunately, it looks like `setupClient()` has already been called, so it should be possible to pass the client name to `p4 changes`.
Specifically, I think this:
.addArgLine("changes -s submitted")
should look more like this:
.addArgLine("-c " + getClientName() + " changes -s submitted") |
Show » |
Change by PMEase JIRA Administrator [05/Dec/14 02:42 AM]
|
Fix Version/s
|
|
5.1.40
[ 11550
]
|
Change by PMEase JIRA Administrator [05/Dec/14 02:42 AM]
|
Field |
Original Value |
New Value |
Status
|
Open
[ 1
]
|
Resolved
[ 5
]
|
Assignee
|
Robin Shen
[ robinshine
]
|
|
Resolution
|
|
Fixed
[ 1
]
|
|