#2121: Allow limited-scope Perforce checkouts
----------------------+------------------------
Reporter: gmcnew | Owner:
Type: undecided | Status: new
Priority: major | Milestone: undecided
Version: 0.8.4p2 | Resolution:
Keywords: p4 |
----------------------+------------------------
Comment (by dustin):
To speak to your two questions:
1. This should be implemented in a master-side P4 step. We've ported
several other VC's to the master side, but since Perforce is proprietary,
we weren't able to do so for P4. Still, there are sufficient examples to
make this clear. Once the port is complete, I expect it will be fairly
trivial to add some new step-constructor parameters (or alter existing
parameters, since the master-side implementation represents a clean break)
to support the functionality you're looking for.
1. As for being maintained - I can only guarantee that any unit tests
you write will continue to pass. Perforce is currently listed as
"Orphaned" in MAINTAINERS.txt:
{{{
Perforce VC
S: Orphaned
U: http://trac.buildbot.net/wiki/p4
}}}
Of course, you're welcome to step up as a maintainer of this component!
--
Ticket URL: <http://trac.buildbot.net/ticket/2121#comment:2>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
Buildbot-commits mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/buildbot-commits
