The P4 build step creates a Perforce client specification and performs an update.
p4base
A view into the Perforce depot without branch name or trailing "...".
Typically "//depot/proj/".
defaultBranch
A branch name to append on build requests if none is specified.
Typically "trunk".
p4port
(optional): the host:port string describing how to get to the P4 Depot
(repository), used as the -p argument for all p4 commands.
p4user
(optional): the Perforce user, used as the -u argument to all p4
commands.
p4passwd
(optional): the Perforce password, used as the -p argument to all p4
commands.
p4extra_views
(optional): a list of (depotpath, clientpath) tuples containing extra
views to be mapped into the client specification. Both will have
"/..." appended automatically. The client name and source directory
will be prepended to the client path.
p4client
(optional): The name of the client to use. In mode='copy' and
mode='update', it's particularly important that a unique name is used
for each checkout directory to avoid incorrect synchronization. For
this reason, Python percent substitution will be performed on this value
to replace %(slave)s with the slave name and %(builder)s with the
builder name. The default is "buildbot_%(slave)s_%(build)s".
p4line_end
(optional): The type of line ending handling P4 should use. This is
added directly to the cliet spec's LineEnd property. The default is
"local".