mirror of
git://code.qt.io/qt/qt5.git
synced 2026-03-17 01:36:32 +08:00
9b481175c4
We pick the oldest build tools we can find because there is lower chance that the produced binaries will be incomaptible with the newer version of MSVC. With the current provisioning design we also cannot change the MSVC version for the each package on demand. Once Enter-VsDevShell is called it litters the powershell environment and blocks the use of Enter-VsDevShell second time. It could be better to run each .ps1 file in own instance of powershell to avoid mixing build environment. Amendsf58afd5476Change-Id: Ie752cfc8b69ed985e61ec16209007dd586611866 Reviewed-by: Samuel Mira <samuel.mira@qt.io> Reviewed-by: Artem Dyomin <artem.dyomin@qt.io> Reviewed-by: Ville Voutilainen <ville.voutilainen@qt.io> (cherry picked from commit84df93d37e) Reviewed-by: Alexey Edelev <alexey.edelev@qt.io>
Continuous Integration ====================== This directory contains files used by Qt's Continuous Integration system (Coin). pre-provisioning ---------------- Contains scripts which are used to install software to tier1 machines manually. E.g. Visual studio installation takes too long to be included to automatic provisioning of tier2 templates. provisioning ------------ Contains scripts that apply to different test machines in order to run automatic tests on them. For Windows scripts, make sure that the machine has "Set-ExecutionPolicy RemoteSigned -Force" set. (Run as admin in PowerShell)