forked from jenkinsci/perforce-plugin
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[FIXED JENKINS-9819] adding option for sync -p
- Loading branch information
Rob Petti
committed
Jun 14, 2011
1 parent
2835992
commit acbfdde
Showing
5 changed files
with
55 additions
and
27 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,12 @@ | ||
<div> | ||
<p> | ||
If you do not want the plugin to update the server side 'have' database, check this box. | ||
</p> | ||
<p> | ||
Typically Perforce keeps track of which files each client has synced down. This isn't always required, and in some cases may prevent the plugin from syncing at all (such as read-only/replicated servers). Enabling this option is equivalent to adding the '-p' flag to the sync command. | ||
</p> | ||
<p>From the Perforce documentation: <i>Populate a client workspace, but do not update the have list. Any file that is already synced or opened is bypassed with a warning message. | ||
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> | ||
</div> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters