[p4] Feature request: P4 job as revision range specifier
p4shawn at gmail.com
Tue Mar 25 17:09:43 PDT 2008
You can setup a daemon to automatically create sparse labels for your jobs
with a specific naming convention... like 'jl-job1234'.
Then you can sync on them with p4 sync @=jl-job1234 or report on them with
p4 files @=jl-job1234 or integrate them with p4 integ -b <branch> -s
@jl-job1234. Be careful with the use of @ vs. @= as you'll get different
results with different commands.
You can find an example of this in the Public Depot here:
I actually haven't implemented this on our live server, but on a test server
this worked fine with around 30k jobs & 90k fixes. The only problem was the
gui clients when you click on the labels tab... but that might be better now
that p4 labels has a -m flag.
On Tue, Mar 25, 2008 at 3:22 PM, Calman, Kevin <Kevin.Calman at acs-inc.com>
> If this hasn't been request in the past, I would like to request the
> following feature from Perforce: allow use of a job in a revision range.
> We use the P4DTI to synchronize P4 jobs to Bugzilla bugs, and then use
> those bugs as atomic units of work to drop code in to builds. It would be
> really useful to be able to sync a workspace to all the changelists in a
> particular bug (job) in a single operation.
> Currently, we use a wrapper script to build a private label from the
> changelists in a job, and then sync that, but it is a drag.
> Opinions herein are exclusively my own, unless you share them.
> Kevin Calman, kevin.calman at acs-inc.com, +1-512-671-2647
> "CONFIDENTIALITY NOTICE: This email message, including any attachments, is
> for the sole use of the intended recipient(s) and may contain confidential
> and privileged information. Any unauthorized review, use, disclosure, or
> distribution is prohibited. If you are not the intended recipient, please
> contact the sender by reply email and destroy all copies of the original
> perforce-user mailing list - perforce-user at perforce.com
More information about the perforce-user