Downloads of v 0.1.1:


Last Update:

25 Jun 2018

Package Maintainer(s):

Software Author(s):

  • Microsoft Corporation




This is not the latest version of VSTS CLI available.

  • 1
  • 2
  • 3

0.1.1 | Updated: 25 Jun 2018



Downloads of v 0.1.1:



Software Author(s):

  • Microsoft Corporation



  • 1
  • 2
  • 3
VSTS CLI 0.1.1

This is not the latest version of VSTS CLI available.

  • 1
  • 2
  • 3

All Checks are Passing

3 Passing Tests

Validation Testing Passed

Verification Testing Passed


Scan Testing Successful:

No detections found in any package files

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

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


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


To uninstall VSTS CLI, run the following command from the command line or from PowerShell:


Deployment Method:

📝 NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Enter Your Internal Repository Url

(this should look similar to

2. Setup Your Environment

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 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. Copy Your Script

choco upgrade vsts-cli -y --source="'INTERNAL REPO URL'" --version="'0.1.1'" [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 vsts-cli -y --source="'INTERNAL REPO URL'" --version="'0.1.1'" 

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0

Exit $exitCode

- name: Install vsts-cli
    name: vsts-cli
    version: '0.1.1'
    state: present

See docs at

chocolatey_package 'vsts-cli' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '0.1.1'

See docs at

cChocoPackageInstaller vsts-cli
    Name     = "vsts-cli"
    Version  = "0.1.1"
    Source   = "INTERNAL REPO URL"

Requires cChoco DSC Resource. See docs at

package { 'vsts-cli':
  ensure   => '0.1.1',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',

Requires Puppet Chocolatey Provider module. See docs at

4. 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 by moderator gep13 on 16 Jul 2018.


VSTS CLI is Visual Studio Team Services (VSTS) new command line experience for managing VSTS resources. You can install it on macOS, Linux, and Windows and run it from the command line.

VSTS CLI is optimized for managing and administering VSTS resources from the command line, and for building automation scripts that work against your VSTS or Team Foundation Server account. This article helps get you started using it, and teaches you the core concepts behind it.

VSTS CLI is supported on Team Foundation Server 2017 update 2 and later.

$ErrorActionPreference = 'Stop';
$toolsDir     = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"

$packageArgs = @{
  packageName   = $env:ChocolateyPackageName
  softwareName  = 'Microsoft VSTS CLI*'
  fileType      = 'msi'
  silentArgs    = "/qn /norestart"
  validExitCodes= @(0, 3010, 1641)
  url           = ""
  checksum      = 'CA03F2178A84C8ABDD99E693FFCBE85BC3E0733A41AB831CA5736FD1894A724F'
  checksumType  = 'sha256'
  destination   = $toolsDir

Install-ChocolateyPackage @packageArgs 

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.

Add to Builder Version Downloads Last Updated Status
VSTS CLI 0.1.4 544 Thursday, November 29, 2018 Approved
VSTS CLI 126 Thursday, November 29, 2018 Approved
VSTS CLI 0.1.3 355 Thursday, September 20, 2018 Approved
VSTS CLI 0.1.1 263 Monday, June 25, 2018 Approved
VSTS CLI 0.1.0-b1 253 Friday, February 2, 2018 Exempted

This release is a bug fix release:

  • Fixes issue where a user can inadvertently put private data into an argument name which would be included in usage telemetry. Argument names are included in telemetry, but argument values are not. This allows us to make investment decisions based on how customers use the CLI. Before this fix a customer could inadvertently send an argument value as an argument name, and that data would be collected and stored in telemetry for a 4 week period. With this fix, we ensure all argument names are valid argument names before reporting the telemetry. If there are any invalid argument names, then no telemetry is sent. This eliminates any chance of inadvertently including private data in the telemetry. Users have always been able to opt out of telemetry collection by using the configure command.
  • Fixes issue where vsts -v or vsts --version no longer worked with latest version of pip due to the use of a deprecated pip API.
  • Fix build command table output when build has no source branch.
  • Change name of --source-branch arg to just --branch on build queue command for consistancy and ease of use.
  • Improved error messaging when project is not specified but is required.
  • Performance improvements when calling commands with the --help or -h argument, by delaying imports to reduce unnecessary module loading.
  • Improved error messages when queueing a build fails.
  • Dependency updates and reaction
  • Other minor fixes.

This package has no dependencies.

Discussion for the VSTS CLI Package

Ground Rules:

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