Welcome to the Chocolatey Community Package Repository! The packages found in this section of the site are provided, maintained, and moderated by the community.
Moderation
Every version of each package undergoes a rigorous moderation process before it goes live that typically includes:
- Security, consistency, and quality checking
- Installation testing
- Virus checking through VirusTotal
- Human moderators who give final review and sign off
More detail at Security and Moderation.
Organizational Use
If you are an organization using Chocolatey, we want your experience to be fully reliable. Due to the nature of this publicly offered repository, reliability cannot be guaranteed. Packages offered here are subject to distribution rights, which means they may need to reach out further to the internet to the official locations to download files at runtime.
Fortunately, distribution rights do not apply for internal use. With any edition of Chocolatey (including the free open source edition), you can host your own packages and cache or internalize existing community packages.
Disclaimer
Your use of the packages on this site means you understand they are not supported or guaranteed in any way. Learn more...

Downloads:
56,681
Downloads of v 2020.2:
533
Last Update:
20 Nov 2020
Package Maintainer(s):
Software Author(s):
- Perforce Software Inc.
Tags:
p4 perforce helix command line client admin- Software Specific:
- Software Site
- Software License
- Software Docs
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download

P4: Helix Command-Line Client
- Software Specific:
- Software Site
- Software License
- Software Docs
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Downloads:
56,681
Downloads of v 2020.2:
533
Maintainer(s):
Software Author(s):
- Perforce Software Inc.
Edit Package
To edit the metadata for a package, please upload an updated version of the package.
Chocolatey's Community Package Repository currently does not allow updating package metadata on the website. This helps ensure that the package itself (and the source used to build the package) remains the one true source of package metadata.
This does require that you increment the package version.
All Checks are Passing
2 Passing Test
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
2. Get the package into your environment-
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 https://chocolatey.org/api/v2. 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
-
Open Source
- Download the Package Download
- Follow manual internalization instructions
-
Package Internalizer (C4B)
- Run
choco download p4 --internalize --source=https://chocolatey.org/api/v2
(additional options) - Run
choco push --source="'http://internal/odata/repo'"
for package and dependencies - Automate package internalization
- Run
3. Enter your internal repository url
(this should look similar to https://chocolatey.org/api/v2)
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'"
$exitCode = $LASTEXITCODE
Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
Exit 0
}
Exit $exitCode
- name: Ensure p4 installed
win_chocolatey:
name: p4
state: present
version: 2020.2
source: STEP 3 URL
See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.
Coming early 2020! Central Managment Reporting available now! More information...
chocolatey_package 'p4' do
action :install
version '2020.2'
source 'STEP 3 URL'
end
See docs at https://docs.chef.io/resource_chocolatey_package.html.
Chocolatey::Ensure-Package
(
Name: p4,
Version: 2020.2,
Source: STEP 3 URL
);
Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.
cChocoPackageInstaller p4
{
Name = 'p4'
Ensure = 'Present'
Version = '2020.2'
Source = 'STEP 3 URL'
}
Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.
package { 'p4':
provider => 'chocolatey',
ensure => '2020.2',
source => 'STEP 3 URL',
}
Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.
salt '*' chocolatey.install p4 version="2020.2" source="STEP 3 URL"
See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.
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 21 Nov 2020.
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 = 'r20.2'
$baseurl = "https://cdist2.perforce.com/perforce/$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.
- p4.2020.2.nupkg (0f9a6bba8639) - ## / 65
- helix-p4-x64.exe (801e89464908) - ## / 71
- helix-p4-x86.exe (e1612b8942a6) - ## / 72
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 | 533 | Friday, November 20, 2020 | Approved |
P4: Helix Command-Line Client 2020.1 | 7956 | Thursday, April 30, 2020 | Approved |
P4: Helix Command-Line Client 2019.2.20200208 | 1745 | Saturday, February 8, 2020 | Approved |
P4: Helix Command-Line Client 2019.2 | 1406 | Thursday, November 21, 2019 | Approved |
P4: Helix Command-Line Client 2019.1.20191118 | 99 | Tuesday, November 19, 2019 | Approved |
P4: Helix Command-Line Client 2019.1 | 3101 | Friday, May 3, 2019 | Approved |
P4: Helix Command-Line Client 2018.2 | 2056 | Wednesday, November 7, 2018 | Approved |
P4: Helix Command-Line Client 2018.1 | 4874 | Tuesday, April 10, 2018 | Approved |
P4: Helix Command-Line Client 2017.2 | 6653 | Wednesday, October 25, 2017 | Approved |
P4: Helix Command-Line Client 2017.1 | 13362 | Saturday, June 17, 2017 | Approved |
P4: Helix Command-Line Client 2016.2 | 7271 | Thursday, January 5, 2017 | Approved |
P4: Helix Command-Line Client 2016.1.0.20161108 | 798 | Tuesday, November 8, 2016 | Approved |
P4: Helix Command-Line Client 2016.1.0.20161004 | 1267 | Wednesday, October 5, 2016 | Approved |
P4: Helix Command-Line Client 2016.1 | 1615 | Wednesday, August 31, 2016 | Approved |
P4: Perforce Command-Line Client 2015.2 | 1157 | Wednesday, January 20, 2016 | Approved |
P4: Perforce Server 2015.1 | 568 | Wednesday, April 1, 2015 | Approved |
P4: Perforce Client and Server 2014.2 | 606 | Saturday, October 18, 2014 | Approved |
P4: Perforce Client and Server 2014.1 | 438 | Wednesday, May 21, 2014 | Approved |
P4: Perforce Client and Server 2013.3 | 417 | Saturday, January 25, 2014 | Approved |
P4: Perforce Client and Server 2013.1 | 369 | Wednesday, May 29, 2013 | Approved |
P4: Perforce Client and Server 2012.2 | 390 | Sunday, February 17, 2013 | Approved |
Copyright © 2019 Perforce Software, Inc.
This package has no dependencies.
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.