BBI-16
Closed
Allow branch specs for POPULATE, COPY, and RECORD_MERGE actions.
The POPULATE, COPY and RECORD_MERGE entries in BBI config files
currently look like:
POPULATE|//Path/One/...|//PathTwo/...|Description
Which translate into:
p4 populate -f //Path/One/... //Path/Two/...
With this change, we'll support:
POPULATE|BRANCH_SPEC|YourBranchSpecName|Description
where BRANCH_SPEC is a literal string. That will translate to:
p4 populate -b YourBranchSpecName
Alternately, specifying:
POPULATE|BRANCH_SPEC-r|YourBranchSpecName|Description
translates to:
p4 populate -r -b YourBranchSpecName
That is, right-to-left, the reverse of the default left-to-right
direction of the branch spec.
The POPULATE, COPY and RECORD_MERGE entries in BBI config files
currently look like:
POPULATE|//Path/One/...|//PathTwo/...|Description
Which translate into:
p4 populate -f //Path/One/... //Path/Two/...
With this change, we'll support:
POPULATE|BRANCH_SPEC|YourBranchSpecName|Description
where BRANCH_SPEC is a literal string. That will translate to:
p4 populate -b YourBranchSpecName
Alternately, specifying:
POPULATE|BRANCH_SPEC-r|YourBranchSpecName|Description
translates to:
p4 populate -r -b YourBranchSpecName
That is, right-to-left, the reverse of the default left-to-right
direction of the branch spec.
- Status
- Closed
- Project
- perforce_software-p4bbi
- Severity
- C
- Reported By
- C. Thomas Tyler
- Reported Date
- 4 months ago
- Modified By
- C. Thomas Tyler
- Modified Date
- 4 months ago
- Owned By
- tom_tyler
- Dev Notes
- 2016-02-27 ttyler: Unsuspended and implemented.
2016-02-26 ttyler: This has been suspended due to lack of immediate
need, but it's still a good thing to do at some point. - Type
- Feature
Log in to comment