mirror of
git://code.qt.io/qt/qt5.git
synced 2026-03-17 17:56:11 +08:00
33ff9ebc9e
When you use the helper to set an envvar in provisioning, you can not reference the machine scoped variable in a later .ps1 script in the same provisoning run using the direct/static reference '$env:NAME', instead you have to use a more verbose method with e.g. 'Get-Item' cmdlet and/or set the envvar additionally to the process scope yourself. This change makes the helper also add process scope to the envvars, this way envvars set in provisioning can be simply referenced with '$env:NAME' in later provisioning scripts, which is consistent with the way you can use SetEnvVar helper in Unix and directly reference the envvar with just its variable name in later .sh scripts. This change also removes duplicate local scope envvar definitions now that Set-EnvironmentVariable helper does it. Pick-to: 6.10 Change-Id: I804fa8f8dfce742a84e8b4bc077f466820589f7e Reviewed-by: Assam Boudjelthia <assam.boudjelthia@qt.io> Reviewed-by: Tero Heikkinen <tero.heikkinen@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)