Helix Core is now P4. Product user interfaces will be updated soon. Learn more >>

P4 for Jenkins Documentation | 1.17.3

# Forced clean and sync

This option is generally not recommended due to its inefficiency.

It should only be used when the integrity of the workspace content is in question. Selecting this option will remove all files from the workspace root, including any existing build history, and then perform a forced synchronization to retrieve the required revisions.

You can configure the sync behavior using the following options:

- Populate have list: Overwrites the Perforce "have list". The "have list" records which files have been synced to the workspace. This is usually used when you are not force syncing and only want the next sync to transfer the changes made since the last time the workspace was synced.
- QUIET Perforce messages: Enables the -q flag for all applicable Perforce P4 Server operations. Summary details will still be displayed.
- Pin build at Perforce Label: When a build is triggered by Polling, Build Now, or an external action, the workspace will only sync to the Perforce label in this field. Any other specified change or label will be ignored. Supports variable expansion, for example ${VAR}. If now is used, or a variable that expands to now, the latest change is used (within the scope of the workspace view). For more information about environment variables, see Variable Expansion.

Your search for returned results