Helix SwarmHelix Swarm
Loading...

build.html

  • //
  • guest/
  • jeff_bowles/
  • faq/
  • build.html #1
  • View
  • Commits
  • Open Download .zip Download (24 KB) 
  1. <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head>
  2.    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
  3.    <meta name="GENERATOR" content="Mozilla/4.05 [en] (X11; U; OSF1 V4.0 alpha) [Netscape]">
  4.    <meta name="Author" content="Jeff A. Bowles"><title>FAQ for integrating Perforce with builds</title></head>
  5. <body><x-html>
  6.  
  7.  
  8. <h1>
  9. FAQ for integrating Perforce with your build scripts</h1>
  10. <p>
  11. Contributed by Jeff Bowles
  12.  
  13. </p><h3>
  14. Note - the intended audience for this FAQ is a shell/perl hacker who writes
  15. or maintains local build scripts and wants to integrate Perforce into them.</h3>
  16. <ol>
  17. <h5>
  18. <b>Labels</b></h5>
  19.  
  20. <li>
  21. <a href="#createlabel">How do I create
  22. a label? What should I include in a label?</a></li>
  23.  
  24. <li>
  25. <a href="#overnightlabels">If I want
  26. to create a new label for each overnight build, how would I do it?</a></li>
  27.  
  28. <li>
  29. <a href="#labels_vs_changenums">Should I
  30. use labels or change numbers to track the contents of overnight builds?</a></li>
  31.  
  32. <li>
  33. <a href="#makepatch">So the release
  34. needs to be remade three months after it went out. What do I do?</a></li>
  35.  
  36. <li>
  37. <a href="#makeofficial">I like this
  38. overnight build and want to officially designate it as a "release" build.
  39. What should I do?</a></li>
  40.  
  41. <li>
  42. <a href="#releasebuild">I need to create a
  43. release build - what's different in that process?</a></li>
  44.  
  45. <h5>
  46. <b>Clients</b></h5>
  47.  
  48. <li>
  49. <a href="#populate_build_area">How do I populate
  50. the build area from a nightly build script? What are the problems that
  51. will come up?</a></li>
  52.  
  53. <h5>
  54. &nbsp;Updating depot files from a script</h5>
  55.  
  56. <li>
  57. <a href="#checkin_logs">How do I
  58. update the depot to include a new log, or to include a new line in a logfile?</a></li>
  59.  
  60. <li>
  61. <a href="#should_I_checkin_logs">Should l check in my log files?
  62. What files might need to be modified and checked in as part of a build?</a></li>
  63.  
  64. <h5>
  65. Putting a release out</h5>
  66.  
  67. <li>
  68. <a href="#backup_for_release">What should I back
  69. up when I put a release out?</a></li>
  70.  
  71. <li>
  72. <a href="#escrow">How do I make
  73. an "escrow" copy of the files (that built the release) for the off-site
  74. vaults?</a></li>
  75.  
  76. </ol>
  77. <hr>
  78.  
  79. <ol>
  80.  
  81. <li>
  82. <a name="createlabel"></a><b>How
  83. do I create a build label? What should I include in a label?</b></li>
  84.  
  85.  
  86.   <ul>
  87.  
  88.  
  89.     <li>
  90. Pick a regular format for the label name, e.g. "<i>bld_xxx_1</i>" where
  91. '<i>xxx</i>' is the name of the codeline you're building and '<i>1</i>'
  92. is just a counter, i.e. the first such label. Remember this format - you'll
  93. need it in the next question!</li>
  94.  
  95.  
  96.  
  97.     <li>
  98. Make the label itself:</li>
  99.  
  100.  
  101.  
  102.  
  103.     <p><tt><font color="#990000">&nbsp;&nbsp;&nbsp; p4 label bld_xxx_1</font></tt>
  104.  
  105. </p>
  106.     <p>It'll dump you into an editor, and you can change the default "Views:"
  107. lines from
  108.  
  109. </p>
  110.     <p><tt><font color="#990000">&nbsp;&nbsp;&nbsp; //depot/...</font></tt>
  111.  
  112. </p>
  113.     <p>to look solely at the codeline you want, e.g.
  114.  
  115. </p>
  116.     <p><tt><font color="#990000">&nbsp;&nbsp;&nbsp; //depot/xxx/...</font></tt>
  117.  
  118. </p>
  119.     <p>Save/Quit the editor.
  120. </p>
  121.     <li>
  122. Populate the label with the file/revision list you want:</li>
  123.  
  124.  
  125.  
  126.  
  127.     <p><tt><font color="#990000">&nbsp;&nbsp;&nbsp; p4 labelsync -l bld_xxx_1&nbsp;
  128. //depot/xxx/...</font></tt>
  129.  
  130. </p>
  131.     <p><font color="#000000">or</font>
  132.  
  133. </p>
  134.     <p><tt><font color="#990000">&nbsp;&nbsp;&nbsp; p4 labelsync -l bld_xxx_1
  135. //depot/...</font></tt>
  136.  
  137. </p>
  138.     <p>In this second example, it's okay to include all files in the depot
  139. - it'll really only include files described in the label spec you edited
  140. when you ran "<tt><font color="#990000">p4 label</font></tt>".
  141. <br>&nbsp;
  142. </p>
  143.     <li>
  144. <b>Always include all files [that are under source management] that are
  145. needed to recreate the build</b> . If your build scripts aren't in codeline
  146. "xxx" you'll want to have the label specification include the directory
  147. where they are, and "<tt><font color="#990000">p4 labelsync</font></tt>"
  148. needs to include them.</li>
  149.  
  150.  
  151.   </ul>
  152.  
  153.  
  154. <hr>
  155. <li>
  156. <a name="overnightlabels"></a><b>If
  157. I want to create a new label for each overnight build, how would I do it?</b></li>
  158.  
  159. <br>&nbsp;
  160.  
  161.   <ol>
  162.     <li>
  163. Make sure you're using a regular name for the label, e.g. "bld_xxx_yyy"
  164. where "xxx" is the codeline name and "yyy" is a counter.</li>
  165.     <li>
  166. Create the first label in the sequence, which would be "bld_xxx_1". See
  167. the previous question for that.</li>
  168.     <li>
  169. In the Unix shell, you would do the following (cut and paste):</li>
  170.     <p><tt><font color="#990000">&nbsp;&nbsp; CodeLineName=xxx</font></tt>
  171. <br><tt><font color="#990000">&nbsp;&nbsp; LabelSpec=tst_${CodeLineName}_</font></tt>
  172. <br><tt><font color="#990000">&nbsp;&nbsp; toplabelnumber=`p4 labels |
  173. grep $LabelSpec | sed "s/^Label $LabelSpec//" | \</font></tt>
  174. <br><tt><font color="#990000">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
  175. sed "s/ .*//" | sort -r -n | head -1`</font></tt>
  176. <br><i><tt><font color="#990000">&nbsp;&nbsp; # at this point, we know
  177. the most recent label in this codeline and just need</font></tt></i>
  178. <br><i><tt><font color="#990000">&nbsp;&nbsp; # to create a new label and
  179. populate it.</font></tt></i>
  180. <br><tt><font color="#990000">&nbsp;&nbsp; TopLabel=$LabelSpec$toplabelnumber</font></tt>
  181. <br><tt><font color="#990000">&nbsp;&nbsp; echo Current Label is $LabelSpec$toplabelnumber</font></tt>
  182. <br><tt><font color="#990000">&nbsp;&nbsp; if [ "$toplabelnumber" != ""
  183. ]</font></tt>
  184. <br><tt><font color="#990000">&nbsp;&nbsp; then</font></tt>
  185. <br><tt><font color="#990000">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
  186. newlabelnumber=`expr $toplabelnumber + 1`</font></tt>
  187. <br><tt><font color="#990000">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
  188. NewLabel=$LabelSpec$newlabelnumber</font></tt>
  189. <br><tt><font color="#990000">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
  190. echo "New Label is $NewLabel"</font></tt>
  191. <br>&nbsp;
  192. <br><tt>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <i><font color="#990000">#
  193. the following two commands are from the previous FAQ item.</font></i></tt>
  194. <br><tt><font color="#990000">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
  195. <u>p4 label -o -t $TopLabel $NewLabel | p4 label -i</u></font></tt>
  196. <br><tt><font color="#990000">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
  197. p4 labelsync -l $NewLabel //depot/...</font></tt>
  198. <br><tt><font color="#990000">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
  199. <i># It's best to obsolete labels that are kinda of old, so we</i></font></tt>
  200. <br><i><tt><font color="#990000">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
  201. # do it here.</font></tt></i>
  202. <br><tt><font color="#990000">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
  203. if [ "$toplabelnumber" -gt 10 ]</font></tt>
  204. <br><tt><font color="#990000">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
  205. then</font></tt>
  206. <br><tt><font color="#990000">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
  207. obsoletelabelnumber=`expr $toplabelnumber - 10`</font></tt>
  208. <br><tt><font color="#990000">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
  209. ObsoleteLabel=$LabelSpec$obsoletelabelnumber</font></tt>
  210. <br><tt><font color="#990000">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
  211. p4 label -d $ObsoleteLabel</font></tt>
  212. <br><tt><font color="#990000">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
  213. fi</font></tt>
  214. <br><tt><font color="#990000">&nbsp;&nbsp; else</font></tt>
  215. <br><tt><font color="#990000">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
  216. echo "There was no label to match!" 1&gt;&amp;2</font></tt>
  217. <br><tt><font color="#990000">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
  218. exit 1</font></tt>
  219. <br><tt><font color="#990000">&nbsp;&nbsp; fi</font></tt>
  220. <br>&nbsp;
  221. </p>
  222.     <li>
  223. Perl hackers will look at the previous "Bourne shell" example and use it
  224. as an example of why you don't want to do string processing in "Bourne
  225. shell". One perl treatment of this follows:&nbsp;
  226. </li>
  227.     <tt><font color="#990000">&nbsp;&nbsp; $CodeLineName = "xxx";</font></tt><br>
  228.     <tt><font color="#990000">&nbsp;&nbsp; $LabelSpec="tst_" . $CodeLineName
  229. . "_";</font></tt>
  230.     <p><tt><font color="#990000">&nbsp;&nbsp; @AllLabels = `p4 labels`;</font></tt>
  231. <br><tt><font color="#990000">&nbsp;&nbsp; @ThisCodeLineLabels = sort(sortrevlabel
  232. grep(/$LabelSpec/, @AllLabels));</font></tt>
  233. <br><tt><font color="#990000">&nbsp;&nbsp; $TopLabelLine = $ThisCodeLineLabels[0];</font></tt>
  234. <br><tt><font color="#990000">&nbsp;&nbsp; $TopLabel = $1 if ($TopLabelLine
  235. =~ /^Label\s(\S+)\s/);</font></tt>
  236. <br><tt><font color="#990000">&nbsp;&nbsp; $TopLabelNumber = $1 if ($TopLabel
  237. =~ /^\S+_(\d+)$/);</font></tt>
  238.  
  239. </p>
  240.     <p><tt><font color="#990000">&nbsp;&nbsp; print "The last label in this
  241. codeline is $TopLabel\n";</font></tt>
  242. <br><tt><font color="#990000">&nbsp;&nbsp; $NewLabelNumber = $TopLabelNumber
  243. + 1;</font></tt>
  244. <br><tt><font color="#990000">&nbsp;&nbsp; $NewLabel = "$LabelSpec$NewLabelNumber";</font></tt>
  245. <br><tt><font color="#990000">&nbsp;&nbsp; print "New Label is $NewLabel\n";</font></tt>
  246. <br><tt><font color="#990000">&nbsp;&nbsp; system("<u>p4 label -o -t $TopLabel
  247. $NewLabel | p4 label -i</u>");</font></tt>&nbsp;&nbsp;&nbsp;<i># in real life, return code would be checked!</i>
  248. <br><tt><font color="#990000">&nbsp;&nbsp; system("p4 labelsync -l $NewLabel
  249. //depot/...");</font></tt>
  250. <br><tt><font color="#990000">&nbsp;&nbsp; if ($TopLabelNumber &gt; 10 )</font></tt>
  251. <br><tt><font color="#990000">&nbsp;&nbsp; {</font></tt>
  252. <br><tt><font color="#990000">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
  253. $ObsoleteLabelNumber = $TopLabelNumber - 10;</font></tt>
  254. <br><tt><font color="#990000">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
  255. $ObsoleteLabel = "$LabelSpec$ObsoleteLabelNumber";</font></tt>
  256. <br><tt><font color="#990000">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
  257. system("p4 label -d $ObsoleteLabel");</font></tt>
  258. <br><tt><font color="#990000">&nbsp;&nbsp; }</font></tt>
  259.  
  260. </p>
  261.     <p><tt><font color="#990000">&nbsp;&nbsp; sub sortrevlabel {</font></tt>
  262. <br><tt><font color="#990000">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
  263. my($labelnum_a, $labelnum_b) = ();</font></tt>
  264. <br><tt><font color="#990000">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
  265. $labelnum_a = $1 if ($a =~ /.*_(\d+)/);</font></tt>
  266. <br><tt><font color="#990000">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
  267. $labelnum_b = $1 if ($b =~ /.*_(\d+)/);</font></tt>
  268. <br><tt><font color="#990000">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
  269. return ($labelnum_b &lt;=&gt; $labelnum_a);</font></tt>
  270. <br><tt><font color="#990000">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
  271. }</font></tt>
  272. </p>
  273.     <li>
  274. <font color="#000000">The underlined part in the above fragments probably
  275. should have a "sed" command between the two 'p4 label' commands, to change
  276. the description for each label.</font></li>
  277.   </ol>
  278.  
  279.  
  280. <hr>
  281. <li>
  282. <a name="labels_vs_changenums"></a><b>Should
  283. I use labels or change numbers to track the contents of overnight builds?</b></li>
  284.  
  285. <br>&nbsp;
  286.  
  287.   <ul>
  288.     <li>
  289. There's no right answer. The command</li>
  290.     <p><tt><font color="#990000">&nbsp;&nbsp;&nbsp; p4 changes -m1 //depot/xxx/...</font></tt>
  291.  
  292. </p>
  293.     <p>will tell a build script what the top change number for codeline 'xxx'
  294. (assuming it's mapped there), so it can parse this output and use that
  295. in build logs and build e-mail. The developer would type:
  296.  
  297. </p>
  298.     <p><tt><font color="#990000">&nbsp;&nbsp; p4 sync @12345</font></tt>
  299.  
  300. </p>
  301.     <p>to pull over all files current as of change #12345, but that has a problem:
  302. it'll pull over all files [that his/her client maps in] as of that revision,
  303. not just the files for codeline 'xxx'. You can tell them to type:
  304.  
  305. </p>
  306.     <p><tt><font color="#990000">&nbsp;&nbsp; p4 sync //depot/xxx/...@12345</font></tt>
  307.  
  308. </p>
  309.     <p>but, by then, you've lost the simplicity that using the change numbers
  310. might've given you.
  311. <br>&nbsp;
  312. </p>
  313.     <li>
  314. You should probably always use labels for release builds - when you create
  315. a release you'll often need to include an additional change to one particular
  316. file that you need to track, and you want the label to include <u>exactly</u>
  317. the files used to build the release on the build client.</li>
  318.   </ul>
  319.  
  320.  
  321. <hr>
  322. <li>
  323. <a name="makepatch"></a><b>So the
  324. release needs to be remade three months after it went out. What do I do?</b></li>
  325.  
  326. <dl>You'll need a slightly-hacked version of your "get the source and do
  327. a build" script. The hacks are:
  328.  
  329.   <ul>
  330.     <li>
  331. It shouldn't use or touch any labels except for the release label you've
  332. remembered to create when you made the release. Delete the lines in the
  333. script that create labels or run "p4 labelsync" on them.</li>
  334.     <li>
  335. Change the line in the script that does the "<tt><font color="#990000">p4
  336. sync -f&nbsp; ...#have</font></tt>" so that it looks like:</li>
  337.     <p><tt><font color="#990000">&nbsp;&nbsp; p4 sync -f&nbsp; //depot/xxx/...@labelname</font></tt>
  338.  
  339. </p>
  340.     <p>where "xxx" is the name of the codeline, and "labelname" is the release
  341. label.
  342. </p>
  343.     <li>
  344. Bug your system administrators about whether compiler versions, OS releases,
  345. etc, have changed since the release was created. Listen carefully to their
  346. answers.</li>
  347.     <li>
  348. Run the script. It should create the original release faithfully, although
  349. most compilers embed timestamps within the .exe and .obj files, so you
  350. might not have byte-for-byte identical files.</li>
  351.     <li>
  352. Rerun your regressions to gain confidence in the newly-built product.</li>
  353.   </ul>
  354. </dl>
  355.  
  356. <hr>
  357. <li>
  358. <a name="makeofficial"></a><b>I like
  359. this overnight build and want to officially designate it as a "release"
  360. build. What should I do?</b></li>
  361.  
  362. <dl>See the previous step - you just need to run "p4 label" (to create
  363. a label) and then "p4 labelsync" to the overnight label or change number
  364. that created the build:
  365.  
  366. <p><tt><font color="#990000">&nbsp;&nbsp; p4 labelsync -l release_label_name&nbsp;
  367. //depot/xxx/...@bld_xxx_23</font></tt>
  368.  
  369. </p><p>or
  370.  
  371. </p><p><tt><font color="#990000">&nbsp;&nbsp; p4 labelsync -l release_label_name&nbsp;
  372. //depot/xxx/...@12345</font></tt>
  373.  
  374. </p><p>The first case is for "overnight build #23 for codeline xxx", if you're
  375. using that convention for overnight builds; the second case is if you use
  376. change numbers to track the overnight build contents.
  377. <br>&nbsp;</p></dl>
  378.  
  379. <hr>
  380. <li>
  381. <a name="releasebuild"></a><b>I need to create
  382. a release build - what's different in that process?</b></li>
  383.  
  384. <br>&nbsp;
  385. <dl>This depends on what packages the release for deployment. If you use
  386. the same build mechanisms for overnight and release builds, you should
  387. only need to do a few steps:
  388.  
  389.   <ul>
  390.     <li>
  391. Run the overnight build script to create the build.</li>
  392.     <li>
  393. Label the build area that created the release, using "p4 label" and then
  394. "p4 labelsync". <i>Pick the 'view' for the label carefully, so that it
  395. doesn't include parts of the depot not included in this release.</i></li>
  396.     <li>
  397. Run "p4 label" a second time on the new label, and change the status of
  398. the label to "locked" so that "p4 labelsync" cannot be run against it accidently.</li>
  399.   </ul>
  400. &nbsp;</dl>
  401.  
  402. <hr>
  403. <li>
  404. <a name="populate_build_area"></a><b>How do
  405. I populate the build area for an overnight build? What are the problems
  406. that will come up?</b></li>
  407.  
  408. <br>&nbsp;
  409.  
  410.   <ul>
  411.     <li>
  412. If the Perforce client root is C:/p4root, and the codeline is C:/p4root/xxx,
  413. then you'll need to do 2-3 things to populate the area prior to building:</li>
  414.     <ul>
  415.       <li>
  416. Make a copy of the scripts that'll do the populating, if there's a chance
  417. that you'll delete them in the next two steps! (Leave a place for your
  418. scripts to stand.)</li>
  419.       <li>
  420. Run the OS command to delete the codeline directory, e.g.</li>
  421.       <p><tt><font color="#990000">&nbsp;&nbsp; del/s&nbsp; &nbsp;c:\p4root\xxx</font></tt>
  422.  
  423. </p>
  424.       <p>it's important to do this if you want a clean build - don't rely on
  425. incremental compile for overnight compiles unless the compilation process
  426. takes many hours.
  427. </p>
  428.       <li>
  429. Repopulate the source:</li>
  430.       <p><tt><font color="#990000">&nbsp;&nbsp; p4 &nbsp;sync&nbsp; -f &nbsp; C:/p4root/xxx/...#have</font></tt>
  431. </p>
  432.       <li>
  433. Update the source to the most recent revisions:</li>
  434.       <p><tt><font color="#990000">&nbsp;&nbsp; p4 &nbsp;sync&nbsp; C:/p4root/xxx/...</font></tt>
  435. </p>
  436.       <li>
  437. <font color="#000000">Update your build labels (or remember the current
  438. change numbers) to reflect this new content.</font></li>
  439.     </ul>
  440. Deleting the entire codeline build tree (and any "obj" or "lib" directories
  441. if they're not directly under C:\p4root\xxx) is important because old object
  442. files often can bite you.
  443. <br>
  444. &nbsp;
  445.     <li>
  446. Most problems that come up in this area have to do with obsolete object/library
  447. files. <u>Entirely removing the source area and repopulating saves you
  448. from this headache completely.</u></li>
  449.   </ul>
  450.  
  451.  
  452. <hr>
  453. <li>
  454. <a name="checkin_logs"></a><b>How
  455. do I update the depot to include a new log, or to include a new line in
  456. a logfile?</b></li>
  457.  
  458. <br>&nbsp;
  459.  
  460.   <ul>
  461.     <li>
  462. To include a new log or edit a file, you should:</li>
  463.     <ul>
  464.       <li>
  465. Open the file for either "add" or "edit";</li>
  466.       <li>
  467. Modify the file in whatever ways make sense;</li>
  468.       <li>
  469. Use "p4 change -o" and "p4 submit -i" to create the submitted change.</li>
  470.     </ul>
  471. An example of this, in a Unix shell script, follows:
  472.  
  473.  
  474.     <p><tt><font color="#990000">&nbsp;&nbsp; operation=add</font></tt>
  475. <br><tt><font color="#990000">&nbsp;&nbsp; filename=newfile.txt</font></tt>
  476. <br><tt><font color="#990000">&nbsp;&nbsp; <u>filetype=ltext</u></font></tt>
  477. <br><tt><font color="#990000">&nbsp;&nbsp; [ -f $filename ] &amp;&amp;
  478. operation=edit</font></tt>
  479. <br><tt><font color="#990000">&nbsp;&nbsp; description="log of build for
  480. `date`"</font></tt>
  481.  
  482. </p>
  483.     <p><tt><font color="#990000">&nbsp;&nbsp; p4 $operation -t $filetype $filename</font></tt>
  484.  
  485. </p>
  486.     <p><tt><font color="#990000">&nbsp;&nbsp; echo New information as of `date`
  487. &gt;&gt; $filename</font></tt>
  488. <br><tt><font color="#990000">&nbsp;&nbsp; <i># this point, we need to
  489. construct the change submission with</i></font></tt>
  490. <br><i><tt><font color="#990000">&nbsp;&nbsp; # an accurate description
  491. in the change text.</font></tt></i>
  492. <br><tt><font color="#990000">&nbsp;&nbsp; p4 change -o&nbsp; &gt; xx.tmp</font></tt>
  493. <br><tt><font color="#990000">&nbsp;&nbsp; (</font></tt>
  494. <br><tt><font color="#990000">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
  495. echo "/^Files:/+1,\$v/$filename/d"</font></tt>
  496. <br><tt><font color="#990000">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
  497. echo "/&lt;enter description here&gt;/s/.*/&nbsp;&nbsp;&nbsp; $description/"</font></tt>
  498. <br><tt><font color="#990000">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
  499. echo w</font></tt>
  500. <br><tt><font color="#990000">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
  501. echo q</font></tt>
  502. <br><tt><font color="#990000">&nbsp;&nbsp; ) | ed - xx.tmp</font></tt>
  503. <br><tt><font color="#990000">&nbsp;&nbsp; p4 submit -i &lt; xx.tmp</font></tt>
  504. <br><tt><font color="#990000">&nbsp;&nbsp; rm xxx.tmp</font></tt>
  505.  
  506. </p>
  507.     <p><font color="#000000"><i>Perl</i> hackers won't see substantial gains
  508. by doing this in <i>perl</i>, and the 'ed' is actually easier from the
  509. shell script.</font>
  510. <br>&nbsp;
  511. </p>
  512.     <li>
  513. <font color="#000000">The underlined part above is important, if the file
  514. you're working with is a giant log file, because giant text files should
  515. include this <u>hint</u> so that the files will be stored in more efficient
  516. ways.</font></li>
  517.   </ul>
  518.  
  519.  
  520. <hr>
  521. <li>
  522. <a name="should_I_checkin_logs"></a><b>Should l check in my
  523. log files? What files might need to be modified and checked in as part
  524. of a build?</b></li>
  525.  
  526. <br>&nbsp;
  527.  
  528.   <ul>
  529.     <li>
  530. There's no good answer for this - log files are usually huge, and can start
  531. eating space quickly. It's probably best to keep them in a disk area that's
  532. backed up regularly, but not to check them in if you can avoid it.</li>
  533.     <li>
  534. If, however, you track overnight builds based on change numbers instead
  535. of labels, you might want to have a file somewhere in the <i>depot</i>
  536. that contains one-line entries of the form:</li>
  537.     <br>
  538.     <tt><font color="#990000">&nbsp;&nbsp; change 12345 - overnight build
  539. for 07/22/98</font></tt><br>
  540.     <tt><font color="#990000">&nbsp;&nbsp; change 12366 - overnight build
  541. for 07/23/98</font></tt><br>
  542. and so on. That should be modified (appended to) by the build scripts
  543. using code similar to the example above. <u>It gets really hard to track
  544. which change corresponded to which nightly build, otherwise.</u><br>
  545. &nbsp;
  546.   </ul>
  547.  
  548.  
  549. <hr>
  550. <li>
  551. <a name="backup_for_release"></a><b>What should
  552. I back up when I put a release out?</b></li>
  553.  
  554. <br>&nbsp;
  555. <br>
  556.   <ul>
  557.     <li>As a minimum, you'll need to back up the source files and build scripts
  558. in Perforce that created the product. This makes several assumptions:
  559.  
  560. Usually, however, <u>you'll probably just want to back up the entire Perforce
  561. depot so that you have a complete snapshot of everything</u>, and then
  562. if you restore from this backup you can refer to current labels such as
  563. the <i>product release label</i> you made when you released the product.
  564. (You can also refer to intermediate build labels if you choose, since they'll
  565. be included in the backup.)
  566.  
  567. <i><font color="#000000">The second and third steps are slight overkill
  568. for many situations, but if you wanna be incredibly paranoid, that's the
  569. approach to take.</font></i>
  570. </li>
  571.     <li>
  572. That the build environment (machine, OS, compilers, etc) are easily recreateable
  573. from media you have in-hand;</li>
  574.     <li>
  575. That, if you only back up the top revision of those files, you won't need
  576. file revision history and the like.</li>
  577.     <li>To make the most comprehensive backup, you'll need to do the following:
  578. </li>
  579.     <li>
  580. Checkpoint the Perforce database and save the checkpoint and the subdirectory
  581. $P4ROOT/depot with all its contents:</li>
  582.     <p><tt><font color="#990000">&nbsp;&nbsp; cd $P4ROOT</font></tt>
  583. <br><tt><font color="#990000">&nbsp;&nbsp; p4d&nbsp;&nbsp; -r&nbsp;&nbsp;
  584. .&nbsp;&nbsp; -jc</font></tt>
  585.  
  586. </p>
  587.     <p><font color="#000000">Note that this is documented in the "FAQ for System
  588. Administrators" and also on-line in the Perforce manuals.</font>
  589. </p>
  590.     <li>
  591. <font color="#000000">Save a copy of the Perforce executables you're using,
  592. server and client versions.</font></li>
  593.     <li>
  594. <font color="#000000">Do a full system backup of the build machine on which
  595. the product was created. This isn't so much to get the source onto media
  596. as to get compilers, OS, etc.</font></li>
  597.     <li>
  598. <font color="#000000">Put this all onto a medium you trust, that'll be
  599. around for a while.</font></li>
  600.     <li>
  601. <font color="#000000">Write the <i>product release label,</i> the one that
  602. you created when you built the product, on the media case. Include with
  603. the case a hard-copy printout of the exact commands you typed to create
  604. the media, e.g. <i>created using "tar rvf".</i></font></li>
  605.   </ul>
  606.  
  607. &nbsp;
  608.  
  609. <hr>
  610. <li>
  611. <a name="escrow"></a><b>How do
  612. I make an "escrow" copy of the files (that built the release) for the off-site
  613. vaults?</b></li>
  614.  
  615. <br>&nbsp;
  616. <br>You can use a label to create an initial fileset that you'll archive.
  617. It's pretty easy:
  618.  
  619.   <ul>
  620.     <li>
  621. Create a label using <tt><font color="#990000">p4 label, <i>escrowlabelname1.0,
  622. </i></font></tt>that maps in only the directories you want. (You'll edit
  623. the label specification to either include as many directories as you choose,
  624. or perhaps the exact file list itself.)</li>
  625.     <li>
  626. Populate the label, using:</li>
  627.     <p><tt><font color="#990000">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
  628. p4 labelsync -l&nbsp; <i>escrowlabelname1.0</i>&nbsp;&nbsp; //buildclientname/...#have</font></tt>
  629.  
  630. </p>
  631.     <p>or,
  632.  
  633. </p>
  634.     <p><tt><font color="#990000">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
  635. p4 labelsync -l&nbsp;&nbsp; <i>escrowlabelname1.0&nbsp;&nbsp;</i> @release_source_label</font></tt>
  636.  
  637. </p>
  638.     <p>The first example relies on the build client having the exact files,
  639. at this moment, that it did when it created the build; the second example
  640. relies on having a label of all the source files that were built to create
  641. the release.
  642. </p>
  643.     <li>
  644. Create a new Perforce client that maps its client area to an empty part
  645. of the disk, and on that new client run the command:</li>
  646.     <br>
  647.     <tt><font color="#990000">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
  648. p4 sync&nbsp; @<i>escrowlabelname1.0</i></font></tt>
  649.     <li>
  650. Back up this new area.</li>
  651.     <li>
  652. Run <tt><font color="#990000">p4 label <i>escrowlabel1.0</i>&nbsp;</font></tt>
  653. and mark the label "locked". This will prevent accidently updates of that
  654. label.</li>
  655.     <li>
  656. When release 2.0 goes out and you need to do this again, follow the same
  657. steps. When you create the label, however, use the original (release 1.0)
  658. escrowlabel as a template, using<tt><font color="#990000">&nbsp; p4&nbsp;
  659. label -t <i>escrowlabel1</i>.0&nbsp;</font></tt> escrowlabel2.0 .</li>
  660.   </ul>
  661. </ol>
  662. </x-html><x-html>
  663.  
  664. <i>Last modified on 7 November 2003.</i>
  665. </x-html></body></html>
# Change User Description Committed
#1 5415 michael Move user FAQ to //guest branch and provide pointers.
Remove old branching FAQ.
Update p...age to reference Perforce Software documentation. «		 19 years ago
//public/perforce/faq/build.html
#7 3870 Jeff Bowles Cleaning up formatting. 21 years ago
#6 3868 Jeff Bowles cleaning up a lot of bullet lists. 21 years ago
#5 1959 Jeff Bowles Minor hacks to clean up links. 23 years ago
#4 112 Laura Wingerd Publish "Branching FAQ"
(pull in changes from //guest/laura_wingerd/perforce/faq/... ) 		26 years ago
#3 27 Jeff Bowles Adding important comment. 26 years ago
#2 20 Jeff Bowles Cleaning up numbered lists. 26 years ago
#1 1 laura Add FAQs.
(Still needs index page.) 		26 years ago