Freestyle jobs are configured using the Jenkins graphical user interface. Once the job is complete you can view the script that Jenkins generates. This is a good way to learn what the scripts contain.
The plugin makes use of the Jenkins Credential store, making it easier to manage the Helix Core server (P4D) connection for multiple Jenkins jobs. For details about creating a Perforce Password Credential or Perforce Ticket Credential, see Add a credential.
- From the Jenkins dashboard, click New item from the sidebar menu.
- Enter a name for the new job in the Enter an item name field at the top of the page.
- Click Freestyle project.
- Click OK to start configuring your new Freestyle job.
- Description (optional): enter a description for the job in the Description field.
- Now configure the freestyle job starting with Source Code Management, see below.
To configure the job to use the Perforce Helix server, click the Perforce Software radio button.
Select the credentials for the job from the Perforce credentials dropdown.
Many of the workspace fields can include environment variables to help define their value. We recommend that variables are used in the Workspace name to enable you to identify builds. For more information about environment variables, see Variable Expansion.
Perforce workspaces support the following behaviors:
- Manual (custom view): Manually define the workspace view, and sync options. Creates the workspace if it does not already exist or updates the workspace spec by setting the various options if it already exists. Jenkins will fill out the workspace root and may override the clobber option. For details about manually configuring your workspace, see Manual workspace.
- Static (static view, master only): Uses a predefined workspace, the workspace must have a valid view and must already exist. The plugin user must either own the workspace or the spec must be unlocked allowing the plugin user to make edits. The workspace view remains static, but Jenkins will update other fields such as the workspace root, and clobber option. For details about using a static predefined workspace, see Static workspace.
- Template (view generated for each node): Uses a specified template to generate the workspace view. The name of the workspace is generated using the Workspace Name Format field. This makes it an ideal choice for Matrix builds. For details about using a template to generate the workspace, see Template workspace.
- Streams (view generated by Perforce for each node): Uses a specified stream to generate the workspace view. The name of the workspace is generated using the Workspace Name Format field. This makes it an ideal choice for Matrix builds. For details about using a stream to generate the workspace, see Streams workspace.
- Spec File (load workspace spec from file in Perforce): Loads the workspace configuration from a depot file containing a client workspace spec. This is the same output as p4 client -o and the Spec depot .p4s format. The name of the Workspace must match the name of the client workspace spec. For details about using a spec file for your workspace, see Spec File workspace.
Perforce populates the workspace with the file revisions needed for the build, the options are:
- Automatic Cleanup and Sync: Use when the PerforceHelix server controls the files in the workspace. This is an efficient option that cleans and syncs file revisions in the workspace. Extra (non versioned files) are removed, missing and modified files are re-added. This option is best for clean builds. For details about the Automatic Cleanup and Sync options, see Automatic Cleanup and Sync.
- Flush Workspace: Use when files in the workspace are not added by the PerforceHelix server. No file Sync or cleanup is attempted and no files are removed, but the workspace "have list" is updated. This is effectively the same as using the p4 sync -k command. For details about the Flush Workspace options, see Flush Workspace.
- Forced Clean and Sync: Not recommended because this option is very inefficient. Use if you do not trust the content of your workspace. Removes all of the files in the workspace root, including the build history, and then force syncs the required files. For details about the Forced Clean and Sync options, see Forced Clean and Sync.
- Graph Force Clean and Sync:PerforceHelix4Git required. Use for PerforceGraph and Hybrid only. Removes all of the files in the workspace root, including the build history, and then force syncs the required files. For details about the Graph Force Clean and Sync options, see Graph Force Clean and Sync.
- Preview Check Only: No file sync or cleanup is attempted, and the Workspace "have list" is not updated. This is effectively the same as using the p4 sync -n command. For details about the Preview Check Only options, see Preview Check Only.
- Sync Only: Use if you have a hand-crafted build environment that you don't want to lose any files from. No cleanup is attempted and the sync will update all files (as CLOBBER is set) to the required revisions. This option is best for incremental builds and is mostly used for Pipeline builds. For details about the Sync Only options, see Sync Only.
Parallel sync enables concurrent transfer of files between Jenkins and the Helix server. Parallel sync can greatly reduce the amount of time it takes to update a workspace, especially when connecting across a high latency network. Parallel sync must be enabled on the Helix server (2014.1 or later). For more information on parallel sync, see Using parallel processing for submits and syncs in Helix Core Server Administrator Guide. Parallel sync is disabled by default, to enable parallel sync:
- Click Advanced.
- Select Enabled.
- The parallel sync settings will depend on the capabilities of the Jenkins build machine and the Helix server:
- Threads: Set the number of threads available for parallel sync.
- Minimum Files: If the number of files being sync'ed is less than this value, parallel sync is not used.
- Minimum Bytes: If the total size of files being sync'ed is less than this value, parallel sync is not used.
When polling is used, changes can be filtered to not trigger a build. If the build has more than one filter, the filters are processed starting from the top of the list of filters. Filters can be dragged up or down the list to change the order they are processed in. Click Add a new build filter and select a filter from the dropdown list, options are:
- Exclude changes from depot path: Changes can be filtered to not trigger a build if all of the files within a change match the specified path. For examples, see Exclude Changes From Depot Path.
- Exclude changes from user: Changes owned by the Perforce Helix server user specified in the filter will not be built.
- Exclude changes from outside Java pattern: Changes can be filtered to not trigger a build if none of the files within a change match the Java patterns (regular expression) listed. For examples, see Exclude Changes From Outside Java Pattern.
- Exclude changes outside view mask: Changes can be filtered to not trigger a build if none of the files within a change are contained in the view mask. For examples, see Exclude Changes Outside view mask.
- Polling per Change: A build is carried out for every change that is submitted. The polling event will only return the oldest unbuilt change, resulting in incremental builds.
Repository browsing allows Jenkins to use an external browser to navigate files and changes associated with a Jenkins build. The Helix Swarm browser is recommended.
To enable the feature, select the browser from the Repository browser dropdown list, and provide the full URL to the browser.
Example of a link to a change in Swarm:
If no triggers are set, Jenkins will build based on the Polling build filters in use.
- Perforce triggered build: A build trigger can be added to the job after you have tested the job and proved that it works correctly. For instructions about configuring a build trigger, see Automatic build using a Perforce triggered build.
- Poll SCM: If you enable Poll SCM, ensure that your Auto build filters are configured to suit regular builds and that the polling frequency is longer than the time the build takes to complete.
It is generally better to use the Perforce triggered build option trigger a build based on an specific event, such as a submitted change.
The P4 Plugin supports unshelving of one or more shelved changes into your Jenkins workspace as a build step. To add unshelving as a build step, click the Add build step button and select Perforce: Unshelve. For more information about Perforce: Unshelve, see Perforce: Unshelve.
Jenkins can carry out a number of actions once the build has completed. If the build has more than one post-build action, the actions are processed starting from the top of the list of actions. Post-build actions can be dragged up or down the list to change the order they are processed in.
Click Add post-build action and select an action from the dropdown list, options are:
- Perforce: ApproveImpl review: Perforce Helix Swarm required. Sets the Swarm review state when the build completes. For more information about using Perforce: ApproveImpl review, see Perforce: ApproveImpl Review.
- Perforce: Cleanup: Select to cleanup the workspace after the build. For more information about using Perforce: Cleanup, see Perforce: Cleanup.
- Perforce: Label build: Jenkins can tag builds automatically when the build completes. The Tags are stored in the Perforce Helix server as Automatic Labels with the label view based on the workspace at the time of tagging. For more information about using Perforce: Label Build, see Perforce: Label Build.
- Perforce: Publish assets: Jenkins can automatically shelve or submit build assets to the Perforce Helix server. For example, you can use this function to publish a PDF of the release notes to the Helix server. For more information about using Perforce: Publish Assets, see Perforce: Publish Assets.
When you have finished configuring the job, click Save.
Now that you have configured your job it is ready to be built. For information about building jobs, see Building Jobs.