Downloads:

1,655

Downloads of v 2018.1:

521

Last Update:

10 Apr 2018

Package Maintainer(s):

Software Author(s):

  • "Perforce Software
  • Inc."

Tags:

admin helix p4 p4d perforce

P4D: Helix Server

2018.1 | Updated: 10 Apr 2018

Downloads:

1,655

Downloads of v 2018.1:

521

Maintainer(s):

Software Author(s):

  • "Perforce Software
  • Inc."

P4D: Helix Server 2018.1

Some Checks Have Failed or Are Not Yet Complete

1 Test Passing and 1 Failing Test


Validation Testing Passed


Verification Testing Failed

Details

To install P4D: Helix Server, run the following command from the command line or from PowerShell:

>

To upgrade P4D: Helix Server, run the following command from the command line or from PowerShell:

>

To uninstall P4D: Helix Server, 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://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://chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade p4d -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 p4d -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 p4d installed
  win_chocolatey:
    name: p4d
    state: present
    version: 2018.1
    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 'p4d' do
  action    :install
  version  '2018.1'
  source   'STEP 3 URL'
end

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


Chocolatey::Ensure-Package
(
    Name: p4d,
    Version: 2018.1,
    Source: STEP 3 URL
);

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


cChocoPackageInstaller p4d
{
   Name     = 'p4d'
   Ensure   = 'Present'
   Version  = '2018.1'
   Source   = 'STEP 3 URL'
}

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


package { 'p4d':
  provider => 'chocolatey',
  ensure   => '2018.1',
  source   => 'STEP 3 URL',
}

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


salt '*' chocolatey.install p4d version="2018.1" 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 10 Apr 2018.

Description

The Helix versioning server stores and manages access to versioned files, tracks user operations and records all activity in a centralized database.


tools\chocolateyInstall.ps1
$packageName = 'p4d'
$url32 = 'http://filehost.perforce.com/perforce/r18.1/bin.ntx86/helix-versioning-engine-x86.exe'
$url64 = 'http://filehost.perforce.com/perforce/r18.1/bin.ntx64/helix-versioning-engine-x64.exe'
$checksum32  = 'bc6a20b374b5e1f774f2eace9da06b27df0cc694786e74149ed50d5720d8e898'
$checksum64  = '8449cda2c8c710c2fd7591f85a769e8b99987f046e0c104f29378dfb84f7e778'

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

Install-ChocolateyPackage @packageArgs
tools\chocolateyUninstall.ps1
$ErrorActionPreference = 'Stop';
 
$packageName = 'p4d'
$registryUninstallerKeyName = '{F8466CD6-8BBA-4AF6-B03C-47D66288D5A1}'
$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
P4D: Helix Server 2017.2 248 Wednesday, October 25, 2017 Approved
P4D: Helix Server 2017.1 285 Saturday, May 20, 2017 Approved
P4D: Helix Server 2016.2 269 Thursday, January 5, 2017 Approved
P4D: Helix Server 2016.1 332 Wednesday, August 31, 2016 Approved

This package has no dependencies.

Discussion for the P4D: Helix Server Package

Ground Rules:

  • This discussion is only about P4D: Helix Server and the P4D: Helix Server 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 P4D: Helix Server, 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