* 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
* 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>
* 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
Use the same file naming scheme for Windows as is used for Ubuntu, where
the file name includes the Operating System name and release, but
not the target platform.
This also encourages downstream consumers to re-use the same files with
alternative targets by extending the `builders` section and using the
`-only` command line option with Packer to specify the build target.
Closes#1636
