Perforce » History » Version 79
Greg Mathis, 04/12/2018 02:22 PM
1 | 1 | Anonymous | h1. Perforce |
---|---|---|---|
2 | 3 | Anonymous | |
3 | 64 | Greg Mathis | Last updated by {{lastupdated_by}}. |
4 | 64 | Greg Mathis | {{lastupdated_at}} |
5 | 64 | Greg Mathis | |
6 | 63 | Greg Mathis | |
7 | 60 | Greg Mathis | The installation executables are listed below. Click on the link to download the appropriate version, and then execute it. |
8 | 56 | Greg Mathis | For Windows 10, use the 64 bit version, "p4vinst64.exe":/attachments/28/p4vinst64.exe |
9 | 58 | Greg Mathis | For Windows 7, use the 32 bit version, "p4vinst.exe":/attachments/56/p4vinst.exe |
10 | 61 | Greg Mathis | |
11 | 1 | Anonymous | |
12 | 30 | Greg Mathis | h2. Step 1 - Run the install file, select "Next" |
13 | 30 | Greg Mathis | !picture425-1.png! |
14 | 32 | Greg Mathis | |
15 | 30 | Greg Mathis | |
16 | 30 | Greg Mathis | h2. Step 2 - Keep default selections, select "Next" |
17 | 30 | Greg Mathis | !picture624-1.png! |
18 | 32 | Greg Mathis | |
19 | 30 | Greg Mathis | |
20 | 30 | Greg Mathis | h2. Step 3 - Set Server to values below, set your User Name, select "Next" |
21 | 30 | Greg Mathis | !picture799-1.png! |
22 | 32 | Greg Mathis | |
23 | 30 | Greg Mathis | |
24 | 30 | Greg Mathis | h2. Step 4 - Select "Install" |
25 | 30 | Greg Mathis | !picture895-1.png! |
26 | 32 | Greg Mathis | |
27 | 1 | Anonymous | |
28 | 12 | Anonymous | h2. Step 5 - Select "Close" |
29 | 1 | Anonymous | !picture655-1.png! |
30 | 32 | Greg Mathis | |
31 | 32 | Greg Mathis | |
32 | 1 | Anonymous | h2. Step 6 - To start Perforce select "P4V" |
33 | 32 | Greg Mathis | !{width:500px}picture843-1.png! |
34 | 32 | Greg Mathis | |
35 | 1 | Anonymous | |
36 | 32 | Greg Mathis | h2. Step 7 - Default startup dialog should appear, should have the proper Server and User set from Perforce installation Step 3 above. Select "OK" |
37 | 15 | Anonymous | !picture639-1.png! |
38 | 32 | Greg Mathis | |
39 | 1 | Anonymous | |
40 | 34 | Greg Mathis | h2. Step 8 - Check the "Trust this fingerprint" button and select "Connect" |
41 | 15 | Anonymous | !picture850-1.png! |
42 | 33 | Greg Mathis | |
43 | 32 | Greg Mathis | |
44 | 35 | Greg Mathis | h2. Step 9 - Enter in your password and select "OK" |
45 | 15 | Anonymous | !picture710-1.png! |
46 | 33 | Greg Mathis | |
47 | 1 | Anonymous | |
48 | 35 | Greg Mathis | h2. Step 10 - Select "No" |
49 | 37 | Greg Mathis | !{width:600px}picture132-1.png! |
50 | 35 | Greg Mathis | |
51 | 35 | Greg Mathis | |
52 | 35 | Greg Mathis | h2. Step 11 - Select "No" |
53 | 37 | Greg Mathis | !{width:600px}picture371-1.png! |
54 | 33 | Greg Mathis | |
55 | 33 | Greg Mathis | |
56 | 38 | Greg Mathis | h2. Step 12 - We need to create a workspace. Go to View Tab, pull down to "Workspaces" |
57 | 38 | Greg Mathis | !{width:600px}picture26-1.png! |
58 | 39 | Greg Mathis | |
59 | 1 | Anonymous | |
60 | 39 | Greg Mathis | h2. Step 13 - Notice a "Workspaces" pane has now appeared on the left side |
61 | 39 | Greg Mathis | !picture343-1.png! |
62 | 39 | Greg Mathis | |
63 | 38 | Greg Mathis | |
64 | 39 | Greg Mathis | h2. Step 14 - Right click in "Workspaces" pane and select "New Workspace ..." |
65 | 39 | Greg Mathis | !picture241-1.png! |
66 | 39 | Greg Mathis | |
67 | 1 | Anonymous | |
68 | 41 | Greg Mathis | h2. Step 15 - Default Workspace name is fine, but change Workspace root: to C:\ and select "OK" |
69 | 40 | Greg Mathis | !picture264-1.png! |
70 | 40 | Greg Mathis | |
71 | 1 | Anonymous | |
72 | 42 | Greg Mathis | h2. Step 16 - You might get the following warning, select "No" |
73 | 40 | Greg Mathis | !picture631-1.png! |
74 | 40 | Greg Mathis | |
75 | 40 | Greg Mathis | |
76 | 50 | Greg Mathis | h2. Step 17 - Now you should see your workspace in the right pane |
77 | 40 | Greg Mathis | !picture623-1.png! |
78 | 40 | Greg Mathis | |
79 | 40 | Greg Mathis | |
80 | 43 | Greg Mathis | h2. Step 18 - But we want to make a change to the workspace. Right click and select "Edit Workspace ...' |
81 | 40 | Greg Mathis | !picture465-1.png! |
82 | 40 | Greg Mathis | |
83 | 40 | Greg Mathis | |
84 | 43 | Greg Mathis | h2. Step 19 - Select the "Text List Box" display style to see the text of Workspace Mappings: |
85 | 40 | Greg Mathis | !picture841-1.png! |
86 | 40 | Greg Mathis | |
87 | 40 | Greg Mathis | |
88 | 45 | Greg Mathis | h2. Step 20 - Edit the text box to as show below, "//depot/.. //<your_workspace_name>/perforce/... |
89 | 40 | Greg Mathis | !picture99-1.png! |
90 | 40 | Greg Mathis | |
91 | 1 | Anonymous | |
92 | 45 | Greg Mathis | h2. Step 21 - Select "Do Not Update" (we will do it manually at first) |
93 | 40 | Greg Mathis | !picture227-1.png! |
94 | 40 | Greg Mathis | |
95 | 40 | Greg Mathis | |
96 | 46 | Greg Mathis | h2. Step 22 - In the right pane, select depot, right click, and select "Get Latest Revision" |
97 | 1 | Anonymous | !picture307-1.png! |
98 | 46 | Greg Mathis | |
99 | 46 | Greg Mathis | |
100 | 68 | Greg Mathis | h2. Step 23 - In a file explorer window, verify you now have a C:\perforce directory and a number of notional subdirectories and placeholder files to kickstart discussions |
101 | 47 | Greg Mathis | !picture78-1.png! |
102 | 40 | Greg Mathis | |
103 | 65 | Greg Mathis | |
104 | 65 | Greg Mathis | h2. Adding Files to Perforce |
105 | 65 | Greg Mathis | |
106 | 68 | Greg Mathis | It's not very obvious how to add files to Perforce. If you have set up things up the "simple" way, the Perforce Depot is a simple mapping to your local drive at c:\perforce, i.e. \depot\... = C:\perforce\... (you can create custom mappings, if you want/need to, just ask Greg) |
107 | 65 | Greg Mathis | |
108 | 67 | Greg Mathis | h2. Step 1 |
109 | 67 | Greg Mathis | |
110 | 68 | Greg Mathis | Let's say I want to add a new GSE Perl script, newTest.pl, to the Perforce depot. The location in the Depot where I would want to add the file is: \depot\EMIRS\software\GSE\perl\. So I place the file in the my local drive at C:\perforce\EMIRS\software\GSE\perl\. |
111 | 65 | Greg Mathis | |
112 | 72 | Greg Mathis | Then bring up Perforce and select the workspace tab view in the left Perforce pane: |
113 | 66 | Greg Mathis | !workspaceView.png! |
114 | 67 | Greg Mathis | |
115 | 67 | Greg Mathis | h2. Step 2 |
116 | 67 | Greg Mathis | |
117 | 69 | Greg Mathis | newTest.pl should be visible in the workspace view. (You may need to hit the refresh icon in the upper left of the Perforce window, if you just added the file) You'll notice the file has just a blank white icon to the left of the file name, and of course, no revision information to the right of the file name. |
118 | 69 | Greg Mathis | |
119 | 69 | Greg Mathis | h2. Step 3 |
120 | 1 | Anonymous | |
121 | 72 | Greg Mathis | Highlight the file name, right click, and select "Mark for Add". Now on the Perforce right pane, with the "Pending" tab selected, you should see newTest.pl in the "default" change list, as shown below: |
122 | 1 | Anonymous | !pending.png! |
123 | 71 | Greg Mathis | |
124 | 71 | Greg Mathis | |
125 | 71 | Greg Mathis | h2. Step 4 |
126 | 71 | Greg Mathis | |
127 | 1 | Anonymous | Highlight the default change list, right click, and select "Submit". Now provide something meaningful in the change list description, and hit the "Submit" button. |
128 | 1 | Anonymous | !submit.png! |
129 | 72 | Greg Mathis | |
130 | 72 | Greg Mathis | |
131 | 72 | Greg Mathis | h2. Step 5 |
132 | 72 | Greg Mathis | |
133 | 73 | Greg Mathis | You should be done adding the file (or multiple files, or directory, or multiple directories) and they should now show up in the depot view (left Perforce pane, select Depot view tab). |
134 | 74 | Greg Mathis | |
135 | 74 | Greg Mathis | |
136 | 77 | Greg Mathis | h2. Creating Labels in Perforce |
137 | 74 | Greg Mathis | |
138 | 75 | Greg Mathis | When we create software releases, we use Perforce labels to tag the individual version of the files in the label. We can then print out this file info is a software release version description document (VDD). |
139 | 75 | Greg Mathis | |
140 | 75 | Greg Mathis | |
141 | 74 | Greg Mathis | h2. Step 1 |
142 | 75 | Greg Mathis | |
143 | 75 | Greg Mathis | In the depot view, highlight the files and/or directories which will comprise the software release. Right click, and select "Labels ..." |
144 | 74 | Greg Mathis | |
145 | 74 | Greg Mathis | !picture121-1.png! |
146 | 1 | Anonymous | |
147 | 1 | Anonymous | |
148 | 77 | Greg Mathis | h2. Step 2 |
149 | 77 | Greg Mathis | |
150 | 77 | Greg Mathis | Create the Label name and then hit the Label button in lower right corner. When it asks to create it, select Yes. |
151 | 76 | Greg Mathis | |
152 | 76 | Greg Mathis | !picture177-1.png! |
153 | 78 | Greg Mathis | |
154 | 78 | Greg Mathis | h2. Step 3 |
155 | 78 | Greg Mathis | |
156 | 78 | Greg Mathis | Verify the new label exists by bringing up the "Labels" tab in the right pane. (View->Labels) |
157 | 78 | Greg Mathis | |
158 | 78 | Greg Mathis | !picture2-1.png! |
159 | 79 | Greg Mathis | |
160 | 79 | Greg Mathis | h2. Step 4 |
161 | 79 | Greg Mathis | |
162 | 79 | Greg Mathis | Listing the file details in a Label seems impossible in the Perforce GUI. (It used to be able to do it). Instead we have to use the command line Perforce interface. Go to a command.exe window and type "p4 files@esimDATP100040" |
163 | 79 | Greg Mathis | |
164 | 79 | Greg Mathis | !picture294-1.png! |
165 | 79 | Greg Mathis | |
166 | 79 | Greg Mathis | |
167 | 79 | Greg Mathis | You can now cut and paste from the command.exe window into a version description document. |