Downloads of v 2021.1:


Last Update:

14 May 2021

Package Maintainer(s):

Software Author(s):

  • Perforce Software Inc.


p4 perforce helix command line client admin

P4: Helix Command-Line Client

  • 1
  • 2
  • 3

2021.1 | Updated: 14 May 2021



Downloads of v 2021.1:


Software Author(s):

  • Perforce Software Inc.

  • 1
  • 2
  • 3
P4: Helix Command-Line Client 2021.1

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed

Validation Testing Passed

Verification Testing Passed


Scan Testing Resulted in Flagged as a Note:

At least one file within this package has greater than 0 detections, but less than 5


To install P4: Helix Command-Line Client, run the following command from the command line or from PowerShell:


To upgrade P4: Helix Command-Line Client, run the following command from the command line or from PowerShell:


To uninstall P4: Helix Command-Line Client, run the following command from the command line or from PowerShell:


NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to

4. Choose your deployment method:

choco upgrade p4 -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:

choco upgrade p4 -y --source="'STEP 3 URL'"

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0

Exit $exitCode

- name: Ensure p4 installed
    name: p4
    state: present
    version: 2021.1
    source: STEP 3 URL

See docs at

chocolatey_package 'p4' do
  action    :install
  version  '2021.1'
  source   'STEP 3 URL'

See docs at

    Name: p4,
    Version: 2021.1,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller p4
   Name     = 'p4'
   Ensure   = 'Present'
   Version  = '2021.1'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'p4':
  provider => 'chocolatey',
  ensure   => '2021.1',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install p4 version="2021.1" source="STEP 3 URL"

See docs at

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...

This package was approved as a trusted package on 14 May 2021.


The P4 command-line client provides access to all Perforce features and functions as an interface for scripting and automated operations.

Customize automation for your development and administrative processes by embedding commands using Perl, Python, or any other scripting language. You can tailor operations for automating Continuous Integration/Continuous Development (CI/CD) to create your ideal workflow.

The Perforce P4 Command-Line Client uses the same commands and syntax on a wide variety of platforms. It automatically translates line ending conventions between operating systems.

$packageName = 'p4'
$version = 'r21.1'
$baseurl = "$version"
$url32 = "$baseurl/bin.ntx86/helix-p4-x86.exe"
$url64 = "$baseurl/bin.ntx64/helix-p4-x64.exe"
$checksum32 = ((Invoke-WebRequest "$baseurl/bin.ntx86/SHA256SUMS" -UseBasicParsing).RawContent.ToString().Split() | Select-String -Pattern 'helix-p4-x86.exe' -SimpleMatch -Context 1,0 ).ToString().Trim().Split()[0]
$checksum64 = ((Invoke-WebRequest "$baseurl/bin.ntx64/SHA256SUMS" -UseBasicParsing).RawContent.ToString().Split() | Select-String -Pattern 'helix-p4-x64.exe' -SimpleMatch -Context 1,0 ).ToString().Trim().Split()[0]

$packageArgs = @{
  packageName    = $packageName
  installerType	 = 'EXE'
  url            = $url32
  url64Bit       = $url64
  checksum       = $checksum32
  checksum64     = $checksum64
  checksumType   = 'sha256'
  checksumType64 = 'sha256'
  silentArgs	 = '/s /v"/qn"'

Install-ChocolateyPackage @packageArgs
$ErrorActionPreference = 'Stop';

$packageName = 'p4'
$softwareName = 'Helix P4 Command-Line Client*'
$installerType = 'MSI' 

$silentArgs = '/qn /norestart'
$validExitCodes = @(0, 3010, 1605, 1614, 1641)
if ($installerType -ne 'MSI') {
  $validExitCodes = @(0)

$uninstalled = $false
[array]$key = Get-UninstallRegistryKey -SoftwareName $softwareName

if ($key.Count -eq 1) {
  $key | % { 
    $file = "$($_.UninstallString)"

    if ($installerType -eq 'MSI') {
      $silentArgs = "$($_.PSChildName) $silentArgs"

      $file = ''

    Uninstall-ChocolateyPackage -PackageName $packageName `
                                -FileType $installerType `
                                -SilentArgs "$silentArgs" `
                                -ValidExitCodes $validExitCodes `
                                -File "$file"
} elseif ($key.Count -eq 0) {
  Write-Warning "$packageName has already been uninstalled by other means."
} elseif ($key.Count -gt 1) {
  Write-Warning "$key.Count matches found!"
  Write-Warning "To prevent accidental data loss, no programs will be uninstalled."
  Write-Warning "Please alert package maintainer the following keys were matched:"
  $key | % {Write-Warning "- $_.DisplayName"}

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
P4: Helix Command-Line Client 2020.2 1513 Friday, November 20, 2020 Approved
P4: Helix Command-Line Client 2020.1 9436 Thursday, April 30, 2020 Approved
P4: Helix Command-Line Client 2019.2.20200208 1769 Saturday, February 8, 2020 Approved
P4: Helix Command-Line Client 2019.2 1450 Thursday, November 21, 2019 Approved
P4: Helix Command-Line Client 2019.1.20191118 127 Tuesday, November 19, 2019 Approved
P4: Helix Command-Line Client 2019.1 5905 Friday, May 3, 2019 Approved
P4: Helix Command-Line Client 2018.2 2148 Wednesday, November 7, 2018 Approved
P4: Helix Command-Line Client 2018.1 5234 Tuesday, April 10, 2018 Approved
P4: Helix Command-Line Client 2017.2 6785 Wednesday, October 25, 2017 Approved

This package has no dependencies.

Discussion for the P4: Helix Command-Line Client Package

Ground Rules:

  • This discussion is only about P4: Helix Command-Line Client and the P4: Helix Command-Line Client package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or P4: Helix Command-Line Client, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus