Downloads:

5,551

Downloads of v 12.0.21005.20160101:

339

Last Update:

01 Jan 2016

Package Maintainer(s):

Software Author(s):

  • Microsoft

Tags:

visualstudiotestagents Workwave-Engineering-Services

visualstudio2013testagents Update 5 (Install)

This is not the latest version of visualstudio2013testagents Update 5 (Install) available.

  • 1
  • 2
  • 3

12.0.21005.20160101 | Updated: 01 Jan 2016

Downloads:

5,551

Downloads of v 12.0.21005.20160101:

339

Maintainer(s):

Software Author(s):

  • Microsoft

  • 1
  • 2
  • 3
visualstudio2013testagents Update 5 (Install) 12.0.21005.20160101

This is not the latest version of visualstudio2013testagents Update 5 (Install) available.

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed


Validation Testing Passed


Verification Testing Failed

Details

Scan Testing Successful:

No detections found in any package files

Details

Deployment Method: Individual Install, Upgrade, & Uninstall

To install visualstudio2013testagents Update 5 (Install), run the following command from the command line or from PowerShell:

>

To upgrade visualstudio2013testagents Update 5 (Install), run the following command from the command line or from PowerShell:

>

To uninstall visualstudio2013testagents Update 5 (Install), 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 https://community.chocolatey.org/api/v2/)


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 https://community.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. Copy Your Script

choco upgrade visualstudio2013testagents -y --source="'INTERNAL REPO URL'" --version="'12.0.21005.20160101'" [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 visualstudio2013testagents -y --source="'INTERNAL REPO URL'" --version="'12.0.21005.20160101'" 
$exitCode = $LASTEXITCODE

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

Exit $exitCode

- name: Install visualstudio2013testagents
  win_chocolatey:
    name: visualstudio2013testagents
    version: '12.0.21005.20160101'
    source: INTERNAL REPO URL
    state: present

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.


chocolatey_package 'visualstudio2013testagents' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '12.0.21005.20160101'
end

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


cChocoPackageInstaller visualstudio2013testagents
{
    Name     = "visualstudio2013testagents"
    Version  = "12.0.21005.20160101"
    Source   = "INTERNAL REPO URL"
}

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


package { 'visualstudio2013testagents':
  ensure   => '12.0.21005.20160101',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',
}

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


4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved by moderator ferventcoder on 03 Jan 2016.

Description

Microsoft Visual Test Agent and Controller for running compiled tests on a node without installing all of Visual Studio.
By default this package installs only the Test Agent. Use the switch /ControllerInsteadofTestAgent to install the Test Controller instead.
If you need both on one node, run the package once with no options and then again with '/ControllerInsteadofTestAgent -Force'

#### Package Parameters
The following package parameters can be set:

* /ControllerInsteadofTestAgent - install the Test Controller instead of just the Test Agent.

These parameters can be passed to the installer with the use of -params.
For example: -params '"/ControllerInsteadofTestAgent"'.
To add Controller to a machine with Agent already installed: -params '"/ControllerInsteadofTestAgent"' -force.


tools\chocolateyinstall.ps1
$ErrorActionPreference = 'Stop'; # stop on all errors

$packageName= 'visualstudio2013testagents'
$toolsDir   = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$url        = 'https://download.microsoft.com/download/B/E/3/BE3CD572-E8B4-48C5-B2C6-D038CB6B1E93/vs2013.5_agts_enu.iso'
$url64      = 'https://download.microsoft.com/download/B/E/3/BE3CD572-E8B4-48C5-B2C6-D038CB6B1E93/vs2013.5_agts_enu.iso'
$silentArgs = "/silent /log $env:temp\vstestagentinstall.log"

$checksum      = $checksum64     ='C0D8789271E254E3B8307A78B6F5DC76532345C1'
$checksumType  = $checksumType64 = 'sha1'

$arguments = @{};
# /ControllerInsteadofTestAgent
$packageParameters = $env:chocolateyPackageParameters;

# Default the values
$ControllerInsteadofTestAgent = $false

# Now parse the packageParameters using good old regular expression
if ($packageParameters) {
    $match_pattern = "\/(?<option>([a-zA-Z]+)):(?<value>([`"'])?([a-zA-Z0-9- _\\:\.]+)([`"'])?)|\/(?<option>([a-zA-Z]+))"
    #"
    $option_name = 'option'
    $value_name = 'value'

    if ($packageParameters -match $match_pattern ){
        $results = $packageParameters | Select-String $match_pattern -AllMatches
        $results.matches | % {
          $arguments.Add(
              $_.Groups[$option_name].Value.Trim(),
              $_.Groups[$value_name].Value.Trim())
      }
    }
    else
    {
      throw "Package Parameters were found but were invalid (REGEX Failure)"
    }

    if ($arguments.ContainsKey("ControllerInsteadofTestAgent")) {
        Write-Host "Installing Test Controller instead of Test Agent because /ControllerInsteadofTestAgent was used."
        $ControllerInsteadofTestAgent = $true
    }
} else {
    Write-Debug "No Package Parameters Passed in";
}

Write-Output "Logs for installers will be in $env:temp"

$AvailableDriveLetter = @(65..90 | ForEach-Object {[char]$_ + ":"}) | Where-Object {@(get-wmiobject win32_logicaldisk | select -expand deviceid) -notcontains $_} | select-object -last 1

try {
    Get-ChocolateyWebFile "$packageName" "$env:temp\vs2013.5_agts_enu.iso" $url -checksum $checksum -checksumType $checksumType -checksum64 $checksum64 -checksumType64 $checksumType64
    imdisk -a -f "$env:temp\vs2013.5_agts_enu.iso"  -m "$AvailableDriveLetter"
    If (!$ControllerInsteadofTestAgent)
    {
      Install-ChocolateyInstallPackage 'visualstudiotestagent' 'exe' $silentArgs "$AvailableDriveLetter\testagent\vstf_testagent.exe"
    }
    Else
    {
      Install-ChocolateyInstallPackage 'visualstudiotestagent' 'exe' "/silent /log $env:temp\vstestcontrollerinstall.log" "$AvailableDriveLetter\TestController\vstf_testcontroller.exe"
    }
    start-sleep -seconds 5
    Try {start-process imdisk -argumentlist "-d -m $AvailableDriveLetter" -ErrorAction SilentlyContinue}
    Catch {#swallow dismount ISO errors
    }
    If (test-path env:ProgramFiles`(x86`)) {$PF = ${env:ProgramFiles(x86)}} Else {$PF = $env:ProgramFiles}
    Install-ChocolateyPath "$PF\Microsoft Visual Studio 12.0\Common7\IDE\CommonExtensions\Microsoft\TestWindow" 'Machine'
    Install-ChocolateyPath "$env:windir\Microsoft.NET\Framework\v4.0.30319" 'Machine'
}
catch {
    throw $_.exception
}

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
visualstudio2013testagents Update 5 (Install) 12.0.21005.20160101 339 Friday, January 1, 2016 Approved
visualstudio2013testagents Update 5 (Install) 12.0.21005.1 380 Monday, December 21, 2015 Approved

The Microsoft Agents do not provide an uninstaller, so neither does this package.


Discussion for the visualstudio2013testagents Update 5 (Install) Package

Ground Rules:

  • This discussion is only about visualstudio2013testagents Update 5 (Install) and the visualstudio2013testagents Update 5 (Install) 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 visualstudio2013testagents Update 5 (Install), 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