Command |
Description |
|
p4 add
|
Open file(s) in a client workspace for addition to the depot. | |
p4 admin
|
Perform administrative operations on the server. | |
p4 branch
|
Create or edit a branch specification and its view. | |
p4 change
|
Create or edit a changelist specification. | |
p4 changelists
|
List submitted and pending changelists. | |
p4 changelist
|
Create or edit a changelist specification. | |
p4 client
|
Create or edit a client workspace specification and its view. | |
p4 clients
|
List all client workspaces currently known to the system. | |
p4 delete
|
Open file(s) in a client workspace for deletion from the depot. | |
p4 depot
|
Create or edit a depot specification. | |
p4 depots
|
Display a list of depots known to the Perforce server. | |
p4 describe
|
Provides information about changelists and the changelists’ files. | |
p4 groups
|
List groups of users. | |
p4 group
|
Add or delete users from a group, or set the maxresults, maxscanrows, and timeout limits for the members of a group. | |
p4 have
|
List files and revisions that have been synced to the client workspace | |
p4 info
|
Display information about the current client and server. | |
p4 integrate
|
Open files for branching or merging. | |
p4 integrated
|
Show integrations that have been submitted. | |
p4 job
|
Create or edit a defect, enhancement request, or other job specification. | |
p4 jobs
|
List jobs known to the Perforce server. | |
p4 label
|
Create or edit a label specification and its view. | |
p4 labels
|
Display list of defined labels. | |
p4 lock
|
Lock an opened file against changelist submission. | |
p4 login
|
Log in to a Perforce server by obtaining a ticket. | |
p4 logout
|
Log out of a Perforce server by removing or invalidating a ticket. | |
p4 passwd
|
Change a user’s Perforce password on the server. | |
p4 rename
|
Renaming files under Perforce. | |
p4 resolve
|
Resolve conflicts between file revisions. | |
p4 revert
|
Discard changes made to open files. | |
p4 set
|
Set Perforce variables in the Windows registry. | |
p4 submit
|
Send changes made to open files to the depot. | |
p4 sync
|
Copy files from the depot into the workspace. | |
p4 tag
|
Tag files with a label. | |
p4 triggers
|
Edit a list of scripts to be run conditionally whenever changelists are submitted, forms are updated, or when integrating Perforce with external authentication mechanisms. | |
p4 user
|
Create or edit Perforce user specifications and preferences. | |
p4 users
|
Print a list of all known users of the current server. | |
p4 verify
|
Verify that the server archives are intact. | |
p4 workspace
|
Create or edit a client workspace specification and its view. |
Tag: Perforce Command Reference
Perforce Quick Facts – Perforce Quick Start Guide
Perforce Quick Facts
Clients
==============================================
P4V: Visual Client – (Included in the P4V Installer)
Provides access to versioned files through a graphical interface and also includes tools for merging and visualizing code evolution.
P4Merge: Visual Merge Tool – (Included in the P4V Installer)
Provides graphical three-way merging and side-by-side file comparisons
P4: Command-Line Client – (Included in the Perforce Server Windows Installer)
(Included in the Perforce Server Windows Installer)
P4Web: Web Client – (Included in the P4Web Installer)
Provides convenient access to versioned files through popular web browsers
Server
================================================
P4D: Server – (Included in the Perforce Server Windows Installer)
Stores and manages access to versioned files, tracks user operations and records all activity in a centralized database.
P4P: Proxy Server – (Included in the Perforce Server Windows Installer)
A self-maintaining proxy server that caches versioned files remotely on distributed networks.
Plug-ins & Integrations
=========================================
P4WSAD: Plug-in for Eclipse and WebSphere Studio
Access Perforce from within the Eclipse IDE and the Rational/WebSphere Studio WorkBench family of products
P4SCC: SCC Plug-in – (Included in the P4V Installer)
Enables you to perform Perforce operations from within IDEs that support the Microsoft SCC API including Visual Studio.
P4EXP: Plug-in for Windows Explorer – (Included in the P4V Installer)
Allows Windows users direct access to Perforce.
P4DTG: Defect Tracking Gateway – (Included in the P4DTG Installer)
Allows information to be shared between Perforce’s basic defect tracking system and external defect tracking systems.
P4GT: Plug-in for Graphical Tools
Provides seamless access to version control for files from within Adobe Photoshop, SoftImage XSI, Autodesk’s 3ds max, and Maya
P4OFC: Plug-in for Microsoft Office
Allows documents to be easily stored and managed in Perforce directly from Microsoft Word, Excel, PowerPoint and Project.
Tools & Utilities
=============================================
P4Report: Reporting System
Supports leading tools such as Crystal Reports, Microsoft Access, and Microsoft Excel, or any reporting tool that interfaces with an ODBC data source.
P4Thumb: Thumbnail Generator
Creates thumbnails of graphics files managed by Perforce and stores the thumbnails in the server for presentation in P4V.
P4FTP: FTP Plug-in
Allows FTP clients like Dreamweaver, Netscape, and Internet Explorer to access files in Perforce depots.’
Links to Download: http://www.perforce.com/perforce/downloads/platform.html
“Cheat Sheet” of Perforce command-line | Perforce command-line Guide
A way to remember data-mining commands | ||||||||||||||||||||||||||||||||||||||||||
The following is a set of questions that will be used during the Perforce training to remind students which “data-mining” commands to use for specific situations. Perforce is a terrific tool, but it’s easy to get lost in the choices between “p4 files” and “p4 changes” and “p4 filelog” and so on. This list can help a great deal.
|
||||||||||||||||||||||||||||||||||||||||||
“Cheat Sheet” of Perforce command-line | ||||||||||||||||||||||||||||||||||||||||||
The following list is a set of helpful commands that anyone can run, but that the person administering the Perforce codelines will be using a lot. They’re included here for quick reference.
|