Houdini 17.5 Nodes TOP nodes

Perforce TOP node

Execute Perforce commands through PDG

On this page

This node acts as a wrapper around Perforce functionality. It provides an interface for executing p4 commands.

Installation

In order to use this node, you must ensure that Perforce is installed on any systems where jobs for this node are going to run.

In addition, the Perforce node must be able to find the p4 executable. When the job runs, it will first look for an environment variable called PDG_PERFORCE. If this variable is defined, the job will use its value as the path to Perforce’s executable. If the PDG_PERFORCE environment variable is not defined, the node will assume that p4 is available via the system’s path.

TOP Attributes

perforceop

string

Indicates the Perforce operation to perform (update, sync, edit, submit, add, change, or test)

overridebin

integer

Specifies whether the user has overriden the default behaviour for determining the location of the P4 executable. When this is set to 1, the work script will use the custom binary path specified by the user.

perforcebin

string

This is set to the custom P4 executable path specified by the user. This is used as the path to the P4 executable when overridebin is set to 1

usefilepattern

integer

For the update, sync, edit, and add operations: when this is 1, the work script will use the file pattern specified by filepattern in the P4 command rather than the list of inputs tagged as 'file'

filepattern

string

For the update, sync, edit, and add operations: when usefilepattern is set to 1, the work script will use this file pattern in the P4 command rather than the list of inputs tagged as 'file'

changelistnum

integer

For the edit, submit, and add operations: specifies the changelist number for the operation

changelistchoice

string

Specifies whether the default changelist or a numbered changelist is being used.

changelistdescription

string

For the submit and change operations: specifies the changelist description

p4configfile

string

Specifies the location of the P4 config file

forcesync

integer

For the sync operation: indicates whether a force sync should be performed

Parameters

Node

Operation

Perforce Operation

This menu is used to select the Perforce command that will be executed.

Use File Pattern

For Perforce commands that require file inputs, this parameter can be used to specify a file pattern. If the file pattern parameter is disabled, there must be results on the upstream work item tagged as 'file'. The node will use those results tagged as 'file' as the input files to the Perforce command.

Force Sync

If performing the sync command, this will enable or disable a force sync.

Changelist

If the Perforce command involves a changelist, this provides the choice of using the default changelist or of using a numbered changelist.

Changelist Number

If the Perforce command involves a changelist and the changelist option is set to 'Numbered', this allows for the changelist number to be specified.

Description

This parameter is used to create the description for any Perforce commands that require a changelist description.

Common

P4 Config File

Specifies the location of a P4 Config file. This will cause the P4CONFIG environment variable to be set in the job’s environment.

Override Perforce Path

This allows the path to the p4 executable to be completely overwritten with a custom path.

Examples

example_top_perforce Example for Perforce TOP node

This example demonstrates how to perform multiple perforce operations.

The following examples include this node.

example_top_perforce Example for Perforce TOP node

This example demonstrates how to perform multiple perforce operations.

TOP nodes