Downloads:

72,224

Downloads of v 2021.3:

1,877

Last Update:

11 Aug 2021

Package Maintainer(s):

Software Author(s):

  • Perforce

Tags:

p4v perforce helix visual client admin

P4V: Helix Visual Client

  • 1
  • 2
  • 3

2021.3 | Updated: 11 Aug 2021

Downloads:

72,224

Downloads of v 2021.3:

1,877

Software Author(s):

  • Perforce

  • 1
  • 2
  • 3
P4V: Helix Visual Client 2021.3

  • 1
  • 2
  • 3

All Checks are Passing

3 Passing Tests


Validation Testing Passed


Verification Testing Passed

Details

Scan Testing Successful:

No detections found in any package files

Details

To install P4V: Helix Visual Client, run the following command from the command line or from PowerShell:

>

To upgrade P4V: Helix Visual Client, run the following command from the command line or from PowerShell:

>

To uninstall P4V: Helix Visual 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 https://community.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

3. Enter your internal repository url

(this should look similar to https://community.chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade p4v -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 p4v -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 p4v installed
  win_chocolatey:
    name: p4v
    state: present
    version: 2021.3
    source: STEP 3 URL

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.


chocolatey_package 'p4v' do
  action    :install
  version  '2021.3'
  source   'STEP 3 URL'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


Chocolatey::Ensure-Package
(
    Name: p4v,
    Version: 2021.3,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller p4v
{
   Name     = 'p4v'
   Ensure   = 'Present'
   Version  = '2021.3'
   Source   = 'STEP 3 URL'
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'p4v':
  provider => 'chocolatey',
  ensure   => '2021.3',
  source   => 'STEP 3 URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


salt '*' chocolatey.install p4v version="2021.3" 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 11 Aug 2021.

Description

Helix Visual Client (P4V) comes with Helix Core –– version control from Perforce.
It allows developers to:

  • Easily customize their workspace.
  • Visualize the flow of change using Perforce Streams.
  • Initiate code reviews.
  • Submit files back into Helix Core.

tools\chocolateyinstall.ps1
$packageName = 'p4v'
$version = 'r21.3'
$baseurl = "https://cdist2.perforce.com/perforce/$version"
$url = "$baseurl/bin.ntx64/p4vinst64.exe"
$checksum64 = ((Invoke-WebRequest "$baseurl/bin.ntx64/SHA256SUMS" -UseBasicParsing).RawContent.ToString().Split() | Select-String -Pattern 'p4vinst64.exe' -SimpleMatch -Context 1,0 ).ToString().Trim().Split()[0]

$packageArgs = @{
  packageName    = $packageName
  installerType	 = 'EXE'
  url            = $url
  checksum       = $checksum64
  checksumType   = 'sha256'
  silentArgs	 = '/s /v"/qn"'
}

Install-ChocolateyPackage @packageArgs
tools\chocolateyuninstall.ps1
$ErrorActionPreference = 'Stop';
 
$packageName = 'p4v'
$registryUninstallerKeyName = '{161E4F2C-F241-4DAB-A40E-7F625435132B}'
$shouldUninstall = $true
 
$local_key     = "HKCU:\Software\Microsoft\Windows\CurrentVersion\Uninstall\$registryUninstallerKeyName"
# local key 6432 probably never exists
$local_key6432   = "HKCU:\Software\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\$registryUninstallerKeyName"
$machine_key   = "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\$registryUninstallerKeyName"
$machine_key6432 = "HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\$registryUninstallerKeyName"
 
$file = @($local_key, $local_key6432, $machine_key, $machine_key6432) `
    | ?{ Test-Path $_ } `
    | Get-ItemProperty `
    | Select-Object -ExpandProperty UninstallString
 
if ($file -eq $null -or $file -eq '') {
    Write-Host "$packageName has already been uninstalled by other means."
    $shouldUninstall = $false
}

$installerType = 'MSI'
# The MSI helper doesn't have a separate argument for specifying the key so silentArgs is used.
# Also note that the helper prepends /X so the key must be listed first
$silentArgs = "$registryUninstallerKeyName /Q"
$validExitCodes = @(0)
 
if ($shouldUninstall) {
 Uninstall-ChocolateyPackage -PackageName $packageName -FileType $installerType -SilentArgs $silentArgs -validExitCodes $validExitCodes
}

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
P4V: Helix Visual Client 2021.2 70 Wednesday, August 11, 2021 Approved
P4V: Helix Visual Client 2021.1 9115 Friday, February 5, 2021 Approved
P4V: Helix Visual Client 2020.3 1045 Tuesday, December 8, 2020 Approved
P4V: Helix Visual Client 2020.2 3463 Friday, August 21, 2020 Approved
P4V: Helix Visual Client 2020.1 2611 Friday, April 17, 2020 Approved
P4V: Helix Visual Client 2019.2 7192 Sunday, November 24, 2019 Approved
Discussion for the P4V: Helix Visual Client Package

Ground Rules:

  • This discussion is only about P4V: Helix Visual Client and the P4V: Helix Visual 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 P4V: Helix Visual 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