With the Perforce integration enabled, you can perform basic Perforce operations from inside RubyMine.
The information provided in the topics listed below assumes that you are familiar with the basics of Perforce version control system.
In this section:
- Using Perforce Integration
- Enabling and Configuring Perforce Integration
- Handling Modified Without Checkout Files
- Integrating Perforce Files
- Resolving Conflicts with Perforce Integration
- Showing Revision Graph and Time-Lapse View
- Using Multiple Perforce Depots with P4CONFIG
- Working Offline
- Attaching and Detaching Perforce Jobs to Changelists
- Checking Perforce Project Status
- A Perforce client is installed on your computer.
- You have an account with the Perforce depot.
- Create a client spec using your Perforce client.
- Get source files from the Perforce depot using your Perforce client.
- As soon as the local working copy is on your computer,
associate your local directory with Perforce.
After that you will be able to open source files for edit, and perform the usual Perforce-related tasks using RubyMine.
- When the Perforce integration with RubyMine is enabled, the item appears on the menu, and on the context menus of the Editor and Project views.
- The files in the folders under the Perforce control are highlighted according to their status. See File Status Highlights for file status highlighting conventions.
- Results of modifications show in the Changes tool window.
- When using the Perforce integration, it is helpful to open the Version Control tool window.
Its Console tab displays the following data:
- All the commands generated based on the settings you specify through the RubyMine user interface.
- Information messages concerning the results of executing generated Perforce commands.
- Error messages.