Plug-in Documentation

Perforce Helix

Overview

The Perforce Helix source configuration plug-in includes a step to import artifacts from a Perforce server as component versions in IBM UrbanCode Deploy.

Compatibility

This plug-in requires version 6.1.0.3 or later of IBM UrbanCode Deploy.

Installation

No special steps are required for installation. See Installing plug-ins in UrbanCode Deploy.

History

Version 6

  • Succeed if most recent version is already imported.
  • Use working directory instead of temp directory for temporary files.

Version 5

Support property file encryption.

Version 4

Version 4 includes a fix for APAR PI57417. The plug-in now checks the agent settings for acceptance of self-signed certificates.

Version 3

Initial release of the plug-in.

Settings

Settings in the Perforce Helix plug-in

Create Component

The following settings are available when you create a component by using the Perforce Helix plug-in.

Settings for creating components
Name Type Description
Do Login/Logout Boolean Use the login and logout commands.
P4 Path String Perforce client executable application. Enter the full path if necessary.
Password Password
Port String Host/Port of the Perforce server.
Preserve Execute Permissions Boolean When enabled, file execute permissions are saved with the files.
Template String Template client specification.
Text File Extensions String A comma-separated list of extensions of files to convert to a new character set on download. Use this field when the operating system that the files are deployed to requires a different character set than the operating system used when uploading files to the server. For example: txt,properties,log
User String

Usage

To create a component by importing from Perforce, complete the following steps. For more information, see Creating components.

  1. On the Components page in IBM UrbanCode Deploy, click Create New Component.
  2. In the Source Config Type list, select Perforce.
  3. Provide all of the necessary information, such as the P4 Path and Template name.
  4. Click Save.
  5. Click the Versions tab for the component.
  6. Click Import New Versions.