Details
-
Sub-task
-
Resolution: Fixed
-
P2: Important
-
None
-
None
-
Qt Installer Sprint 39, Qt Installer Sprint 40, Qt Installer Sprint 41, Qt Installer Sprint 42, Qt Installer Sprint 45, Qt Installer Sprint 56, Qt Installer Sprint 57, Qt Installer Sprint 58, Qt Installer Sprint 59, Qt Installer Sprint 60, Qt Installer Sprint 64, Qt Installer Sprint 65, Qt Installer Sprint 67, Qt Installer Sprint 68, Qt Installer Sprint 69, Qt Installer Sprint 70
Description
kamartti Please specify
Once the sdktool split changes are deployed into our staging area we essentially lose the capability to test the update from scratch. I.e. the state before the sdktool update. Although the initial state can be still installed from production (where the sdktool split update has not landed yet) it may become tricky to use the correct combination of --set-temp-repo arguments.
If possible for RTA, run the installations per macos/linux/windows and save the state by some means. E.g. create a .git repository of the installation and commit a tag of the initial state. Q: Where to store the initial installation for tests?
Attachments
| For Gerrit Dashboard: QTBUG-106554 | ||||||
|---|---|---|---|---|---|---|
| # | Subject | Branch | Project | Status | CR | V |
| 436090,15 | IFW: add function for launching maintenancetool with parameters | master | qtqa/tqtc-qt-rta | Status: MERGED | +2 | 0 |
| 441243,3 | IFW: sdktool split test for installing, updateing and adding component | master | qtqa/tqtc-qt-rta | Status: MERGED | +2 | 0 |