Notices: This section not yet converted to new layout. Download stats are rolling back out.

jFrog Artifactory OSS

Package test results have failed.

This package was rejected on 5/24/2019. The reviewer chocolatey-ops has listed the following reason(s):

DarwinJS (maintainer) on 19 Apr 2019 11:44:12 +00:00:

User 'DarwinJS' (maintainer) submitted package.

chocolatey-ops (reviewer) on 19 Apr 2019 12:18:54 +00:00:

Artifactory has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.


Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.

  • Package contains dependencies with no specified version. You should at least specify a minimum version of a dependency. More...

chocolatey-ops (reviewer) on 19 Apr 2019 14:06:33 +00:00:

Artifactory has failed automated testing.
This is not the only check that is performed so check the package page to ensure a 'Ready' status.
Please visit for details.
The package status will be changed and will be waiting on your next actions.

  • NEW! We have a test environment for you to replicate the testing we do. This can be used at any time to test packages! See
  • Please log in and leave a review comment if you have questions and/or comments.
  • If you see the verifier needs to rerun testing against the package without resubmitting (a issue in the test results), you can do that on the package page in the review section.
  • If the verifier is incompatible with the package, please log in and leave a review comment if the package needs to bypass testing (e.g. package installs specific drivers).
  • Automated testing can also fail when a package is not completely silent or has pop ups (AutoHotKey can assist - a great example is the VeraCrypt package).
  • A package that cannot be made completely unattended should have the notSilent tag. Note that this must be approved by moderators.

chocolatey-ops (reviewer) on 09 May 2019 14:09:40 +00:00:

We've found Artifactory v6.9.1 in a submitted status and waiting for your next actions. It has had no updates for 20 or more days since a reviewer has asked for corrections. Please note that if there is no response or fix of the package within 15 days of this message, this package version will automatically be closed (rejected) due to being stale.

Take action:
* Log in to the site and respond to the review comments.
* Resubmit fixes for this version.
* If the package version is failing automated checks, you can self-reject the package.

If your package is failing automated testing, you can use the chocolatey test environment to manually run the verification and determine what may need to be fixed.

Note: We don't like to see packages automatically rejected. It doesn't mean that we don't value your contributions, just that we can not continue to hold packages versions in a waiting status that have possibly been abandoned. If you don't believe you will be able to fix up this version of the package within 15 days, we strongly urge you to log in to the site and respond to the review comments until you are able to.

chocolatey-ops (reviewer) on 24 May 2019 14:09:44 +00:00:

Unfortunately there has not been progress to move Artifactory v6.9.1 towards an approved status within 15 days after the last review message, so we need to close (reject) the package version at this time. If you want to pick this version up and move it towards approval in the future, use the contact site admins link on the package page and we can move it back into a submitted status so you can submit updates.

Status Change - Changed status of package from 'submitted' to 'rejected'.

Open source vesion of jFrog binary artifact repository including Nuget.


  • tools\chocolateyinstall.ps1 Show
    #Reread Environment In Case JDK dependency just ran
    $version = '6.9.1'
    $url = "$;bt_package=jfrog-artifactory-oss-zip"
    $checksum = '83E99303990A444AADBDA36CE5279640F17F99672917200CB1A62B13E5ECAE82'
    $checksumtype = 'sha256'
    $validExitCodes = @(0)
    $packageName= 'artifactory'
    $versionedfolder = "artifactory-oss-$version"
    $toolsDir   = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
    $TargetFolder = "$env:ProgramData\artifactory"
    $ExtractFolder = "$env:temp\jfrogtemp"
    $servicename = 'artifactory'
    If ([bool](Get-Service $servicename -ErrorAction SilentlyContinue))
      Write-Warning "Artifactory is already present, shutting it down so that we can upgrade it."
      Stop-Service $servicename -force
      pushd "$TargetFolder\bin"
      Start-ChocolateyProcessAsAdmin "/c `"$TargetFolder\bin\uninstallservice.bat`"" "cmd.exe" -validExitCodes $validExitCodes
    Write-Host "Ensuring Java is Present and that JDK_HOME is setup..."
    If (!(Test-Path Env:JDK_HOME))
      If (Test-Path "$env:ProgramW6432\Java")
        $JavaPath = (dir 'C:\Program Files\Java\' | sort-object name | select -last 1).fullname
        If ($JavaPath)
          Write-Host "Found JDK at $JavaPath, setting up JDK_HOME..."
          Install-ChocolateyEnvironmentVariable -VariableName 'JDK_HOME' -VariableValue "$JavaPath" -VariableType 'Machine'
          Install-ChocolateyEnvironmentVariable -VariableName 'JDK_HOME' -VariableValue "$JavaPath" -VariableType 'Process'
          Throw "Java is not installed at `"$env:ProgramFiles\Java`", cannot find java, cannot continue"
        Throw "Cannot find variable JDK_HOME nor Java itself, cannot continue..."
    If (Test-Path "$ExtractFolder") {Remove-Item "$ExtractFolder" -Recurse -Force}
    Install-ChocolateyZipPackage -PackageName $packageName -unziplocation "$ExtractFolder" -url $url -checksum $checksum -checksumtype $checksumtype -url64 $url -checksum64 $checksum -checksumtype64 $checksumtype
    Rename-Item "$ExtractFolder\$versionedfolder" "$ExtractFolder\artifactory"
    Copy-Item "$ExtractFolder\artifactory" "$env:programdata" -Force -Recurse
    Remove-Item "$ExtractFolder\artifactory" -Force -Recurse
    #remove the pause from installservice.bat
    ((Get-Content "$TargetFolder\bin\installservice.bat") -replace '& pause', '') -replace 'pause', ''| Set-Content "$TargetFolder\bin\installservice.bat"
    pushd "$TargetFolder\bin"
    $output=(& ./installservice.bat)
    write-host "Results from artifactory's installservice.bat:"
    Write-host "$($output | out-string)"
    Install-ChocolateyEnvironmentVariable 'ARTIFACTORY_HOME' "$TargetFolder\bin" -VariableType 'Machine'
    Install-ChocolateyEnvironmentVariable 'ARTIFACTORY_HOME' "$TargetFolder\bin" -VariableType 'Process'
    If ([bool]!($output -ilike '*has been installed*'))
      Write-host "Artifactory install failed with this message:"
      Throw "Artifactory installer failed."
    $ArtifactoryServiceRegKey = 'HKLM:System\CurrentControlSet\Services\Artifactory'
    If (Test-Path $ArtifactoryServiceRegKey)
      Write-Host "Cleaning up the invalid characters that installservice.bat puts in the Artifactory service definition registry key..."
      #$CleanedValue = (Get-ItemProperty $ArtifactoryServiceRegKey | Select -Expand ImagePath) -replace '[^\p{L}\p{Nd}///_/ /:/./\\/-]', ''
      Set-ItemProperty $ArtifactoryServiceRegKey -Name ImagePath -Value "$TargetFolder\bin\artifactory-service.exe //RS//Artifactory"
      Throw "Artifactory installer failed."
    $service = Start-Service $servicename -PassThru
    Write-Host "Waiting for Artifactory service to be completely ready"
    $Service.WaitForStatus('Running', '00:02:00')
    If ($Service.Status -ine 'Running')
      Write-Warning "The Artifactory service ($servicename) did not start."
      #Even though windows reports service is ready - web url will not respond until Artifactory is actually ready to serve content
      Start-Sleep 120
    Write-Warning "`r`n"
    Write-Warning "***************************************************************************"
    Write-Warning "*  You can manage the repository by visiting http://localhost:8081/artifactory"
    Write-Warning "*  The default user is 'admin' with password 'password'"
    Write-Warning "*  Artifactory availability is controlled via the service `"$servicename`""
    Write-Warning "*  Use the following command to open port 8081 for access from off this machine (one line):"
    Write-Warning "*   netsh advfirewall firewall add rule name=`"Nexus Repository`" dir=in action=allow "
    Write-Warning "*   protocol=TCP localport=8081"
    Write-Warning "***************************************************************************"
  • tools\chocolateyuninstall.ps1 Show
    $validExitCodes = @(0)
    $packageName= 'artifactory'
    $TargetFolder = "$env:ProgramData\artifactory"
    $servicename = 'artifactory'
    If ([bool](Get-Service $servicename -ErrorAction SilentlyContinue))
      Stop-Service $servicename -force
    If (Test-Path "$TargetFolder\bin\uninstallservice.bat")
      pushd "$TargetFolder\bin"
      Start-ChocolateyProcessAsAdmin "/c `"uninstallservice.bat`"" "cmd.exe" -validExitCodes $validExitCodes
    Remove-Item $TargetFolder -Recurse -Force

Virus Scan Results

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.


Package Maintainer(s)

Software Author(s)

  • jFrog




Release Notes

- uses JRE rather than JDK package for java
- captures and error checks installartifactory.bat output
- fixes invalid characters that artifactory's installservice.bat put in artifactory registry key

Version History

Version Downloads Last updated Status
jFrog Artifactory OSS 5.9.3 298 Sunday, March 25, 2018 approved
jFrog Artifactory OSS 5.5.2 279 Monday, November 6, 2017 approved
jFrog Artifactory OSS 4.13.0 476 Saturday, September 24, 2016 approved
jFrog Artifactory OSS 4.10.0 210 Monday, August 1, 2016 approved
jFrog Artifactory OSS 4.5.1 262 Saturday, February 27, 2016 approved

Discussion for the jFrog Artifactory OSS Package

Ground rules:

  • This discussion is only about jFrog Artifactory OSS and the jFrog Artifactory OSS 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 jFrog Artifactory OSS, 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 uses cookies to enhance the user experience of the site.