Downloads of v 0.7.6:


Last Update:

20 Feb 2018

Package Maintainer(s):

Software Author(s):

  • Bojan Rajkovic


volley pastebin commandline

Volley CLI Client

  • 1
  • 2
  • 3

0.7.6 | Updated: 20 Feb 2018



Downloads of v 0.7.6:



Software Author(s):

  • Bojan Rajkovic

  • 1
  • 2
  • 3
Volley CLI Client 0.7.6

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed

Validation Testing Passed

Verification Testing Failed


Scan Testing Successful:

No detections found in any package files


To install Volley CLI Client, run the following command from the command line or from PowerShell:


To upgrade Volley CLI Client, run the following command from the command line or from PowerShell:


To uninstall Volley CLI 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 volley -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 volley -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 volley installed
    name: volley
    state: present
    version: 0.7.6
    source: STEP 3 URL

See docs at

chocolatey_package 'volley' do
  action    :install
  version  '0.7.6'
  source   'STEP 3 URL'

See docs at

    Name: volley,
    Version: 0.7.6,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller volley
   Name     = 'volley'
   Ensure   = 'Present'
   Version  = '0.7.6'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'volley':
  provider => 'chocolatey',
  ensure   => '0.7.6',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install volley version="0.7.6" 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 03 Jul 2018.


A command line client for Volley, a small, but flexible, pastebin similar to

$ErrorActionPreference = 'Stop'; # stop on all errors

$packageName = "volley"
$toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$url = ""
$url64 = ""
$checksumType = "SHA256"
$checksum = "E0F75B306504DBBF5356D334C68C93273462C97DD720A4590F3E75AA20C81B54"
$checksum64 = "BD53BEBCA589C9BF1DD86CF072DCC99445FF2DD5F62093A302CB760ADA78D7EB"

# despite the name "Install-ChocolateyZipPackage" this also works with 7z archives
Install-ChocolateyZipPackage `
  -PackageName $packageName `
  -UnzipLocation "$toolsDir" `
  -Url "$url" `
  -Url64 "$url64" `
  -Checksum $checksum `
  -ChecksumType $checksumType `
  -Checksum64 $checksum64 `
  -Checksum64Type $checksumType

$files = get-childitem $toolsDir -include *.exe -recurse

foreach ($file in $files) {
  if ($file.Name -eq "Volley.Client.exe") {
    #generate an ignore file
    New-Item "$file.ignore" -type file -force | Out-Null

Install-BinFile `
  -Name volley `
  -Path (Join-Path $toolsDir "Volley.Client.exe")
$ErrorActionPreference = 'Stop'; # stop on all errors

$packageName = "volley"
Uninstall-BinFile $packageName

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
Volley CLI Client 0.7.0 202 Monday, February 19, 2018 Approved
Volley CLI Client 0.6.3-alpha 215 Saturday, February 17, 2018 Exempted
Volley CLI Client 0.6.0-alpha 201 Saturday, February 17, 2018 Exempted

This package has no dependencies.

Discussion for the Volley CLI Client Package

Ground Rules:

  • This discussion is only about Volley CLI Client and the Volley CLI 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 Volley CLI 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