* Set AGENT_TOOLSDIRECTORY in packer template
This was set in the ruby installer but it is referenced elsewhere so I
believe it makes the most sense to have this set centrally in the packer
template to be referenced across multiple scripts.
* Fix typo
* Capitalize env var in ws2016 template for consistency
* Set AGENT_TOOLSDIRECTORY in Initialize-VM.ps1
* Add missing env var for AGENT_TOOLSDIRECTORY in step in ws2016 template
* Rework Android NDKs
* Minor fix
* Fix variable name
* Minor fixes
* Reword Android env vars table
* Remove Android env vars table from doc file
* Rework to use only major ndk versions in toolset
* Fix ndk paths
* Fix win2016 toolset
* Refactor
* Minor fix
* Fix ndk tests
* Add more docker tests
* Rework tools installation and test
* remove docker tests from tools
* get back kind installation
* transform kind download link to string
* add Add-MachinePathItem after kind installation
* Removing 'ImageVersion' as an env var as we already use 'IMAGE_VERSION'. The env var is only used SoftwareReport.Generator script.
* Adding IMAGE_VERISON to SoftwareReport.Generator
* Adding IMAGE_VERISON to SoftwareReport.Generator
* Chnaging the way the env vars are used to floow the same pattern throughout
Co-authored-by: Jose Mosquera <jose.mosquera@dotdigital.com>
The `npm_config_cache` env, if set, will have highest priority, and harder to change.
One way to un-set this is add a global workflow env, like:
```
env:
npm_config_cache: ''
```
This commit change the cache config to use `npm config set cache $CachePath --global`,
which should save the path under the global npmrc at: `C:\npm\prefix\etc\npmrc`,
and allow easier later reset with user/repo level `.npmrc` files.
For the record, my usage is to unify all platform's npm cache to `~/.npm/`,
then use the same cache action config on all platform to cache the folder.
* install the latest version
* Revert "install the latest version"
This reverts commit ddf40964b55a65010099ea11f0f1ab0921128970.
* define mingw 8.1.0 version
* Add BizTalk Project Build components, including msi and vsix.
* Add BizTalk Build Components to software report.
* Use registry/folder check replace actually BizTalk Project building for testing purpose.
* Remove unnecessary try/catch.
* Make sure BizTalk related software report only for Windows 2019 OS.
* Add statement to make sure BizTalk test only invoked in Win19 env.
* Fix test failue when no test runs use "skip"
* Update the TestName to be identity to BizTalk.Test.ps1
