VSTS CLI release notes
May 30, 2018
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.
November 15, 2017
This is the preview release of VSTS CLI. Preview applies to these command modules:
- Build (commands to work with and manage Visual Studio Team Services builds.)
- Code (commands to work with and manage Visual Studio Team Services code repositories.)
- Project (commands to work with and manage Visual Studio Team Services team projects.)
- Work (commands to work with and manage Visual Studio Team Services work items.)
These command modules can be used in production and are supported by standard Microsoft SLA.
You can ask questions and report issues on the VSTS developer community website using the vsts-cli tag. You can provide feedback from the command line with the
vsts feedback command.
The commands in these modules are stable and the syntax is not expected to change in upcoming releases of this version of VSTS CLI.
To verify the version of the CLI, use
vsts --version. The output lists the version of the CLI itself, the individual command modules, and the versions of Python and GCC that you're using.
vsts-cli (0.1.0b0) knack (0.2.0) vsts (0.1.0b0.dev4407458) vsts-cli-build (0.1.0b0) vsts-cli-build-common (0.1.0b0) vsts-cli-code (0.1.0b0) vsts-cli-code-common (0.1.0b0) vsts-cli-common (0.1.0b0) vsts-cli-team (0.1.0b0) vsts-cli-team-common (0.1.0b0) vsts-cli-work (0.1.0b0) vsts-cli-work-common (0.1.0b0) Python (Windows) 3.6.2 (v3.6.2:5fd33b5, Jul 8 2017, 04:57:36) [MSC v.1900 64 bit (AMD64)] Python location 'C:\Files\Sdk\cli\python.exe' Legal docs and information: https://aka.ms/vsts-cli-eula
You can report issues in the following ways:
- Report issues on the VSTS developer community website using the vsts-cli tag.
- Provide feedback from the command line with the