[JENKINS-9819] adding note to docs explaining that perforce doesn't a…

…llow -f and -p at the same time during syncing
jenkinsci · Jul 15, 2011 · 21db3c4 · 21db3c4
1 parent 74e23f1
commit 21db3c4
Showing 1 changed file with 2 additions and 0 deletions.
diff --git a/src/main/webapp/help/dontUpdateServer.html b/src/main/webapp/help/dontUpdateServer.html
@@ -9,4 +9,6 @@
 This option is typically used for workspaces used in processes (such as certain build or publication environments) where there is no need to track the state of the workspace after it has first been synced.</i>
 See the rest of the doc here: <a href="http://www.perforce.com/perforce/doc.current/manuals/cmdref/sync.html">here</a>.
   </p>
+  <p><b>Note:</b> For whatever reason, perforce has decided that the -p option needs to be mutually exclusive of the -f option (even though they are functionally unrelated). As a result, you can't force sync and use -p at the same time. If you need to do a full resync while using the -p option, it's recommended that you delete the perforce client and let the plugin recreate it (assuming you are allowing it to manage the client workspace).
+  </p>
 </div>