* Move choco installation list into toolset
* Add a condition to Install-CommonUtils.ps1
* Rename tests and revert Bazel to single script
* Return Install-Bazel.ps1 to windows2016.json and windows2019.json
* Remove condition and Write-Host command from Install-CommonUtils.ps1
* Reset Install-Bazel.ps1 to be the same as in main
* Update choco.common_packages in toolset-2016.json and toolset-2019.json
Co-authored-by: Nikita Bykov <v-nibyko@microsoft.com>
* Switch android installation to use cmdline-tools
* Rename update-android sdk to install-android sdk as for the other OSs
* Remove cmdline-tools installation from toolset as it's installed
* Regenerate licenses for the new sdkmanager
* Add tests to check that both sdkmanagers are available
* Simplify Get-AndroidInstalledPackages function to use list_installed
* Resolve nitpicks from @AlenaSviridenko
* Add extra lines to separate comments from the code
* Remove extra line after $androidNDKs
* Modify software report to output any version number
* Change regex pattern to output the group
* Currently the function returns 4. instead of 4.0, this change fixes it
* Add ShouldReturnZeroExitCodeWithParam function and a new set of tests for MSYS2 tools
* Change get-command -> Get-Command
* Remove elevated user, return original path after msys installation and tests, resolve nitpicks
* Add BeforeEach and AfterEach blocks
These blocks change the path before each test
and return the original path after each test
* Change get-command -> Get-Command
* Trying to handover additional parameters
* Make restriction to agent ip configurable
* Added additional parameter to all other packer files
* Added note about new parameter's incompatibility with other parameters to command line help
* Added line break for better readability
Co-authored-by: Mikhail Timofeev <48208649+miketimofeev@users.noreply.github.com>
Co-authored-by: Mikhail Timofeev <48208649+miketimofeev@users.noreply.github.com>
* 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>
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
