Installer test of the single setup on a clean Windows #72

Open
opened 2026-11-16 15:32:33 +01:00 by Alby96 · 0 comments
Owner

Left over from #70. These checks could not run on the development PC, because Chronos 1.0 is installed there for all users:

  • .gitea/scripts/installer-test.ps1: install, upgrade, add or remove a program, legacy Uploader and Server 1.0.
  • The packed Chronos-Setup-<v>.exe by hand: choose the programs, install, run, update in place, uninstall.
  • The real 1.0 → 1.1 upgrade of an all-users install. On the development PC this needs the owner's UAC approval. Check that the archive, the database and the settings are kept and that migration 0011 runs.

Where to run them:

  • on a clean Windows PC or VM;
  • or in the CI windows job once a Windows runner is registered (WINDOWS_RUNNER).

Owner action that unblocks part of this: run Chronos-Setup-1.1.1.exe on the development PC and approve UAC.

Left over from #70. These checks could not run on the development PC, because Chronos 1.0 is installed there for all users: - [ ] `.gitea/scripts/installer-test.ps1`: install, upgrade, add or remove a program, legacy Uploader and Server 1.0. - [ ] The packed `Chronos-Setup-<v>.exe` by hand: choose the programs, install, run, update in place, uninstall. - [ ] The real 1.0 → 1.1 upgrade of an all-users install. On the development PC this needs the owner's UAC approval. Check that the archive, the database and the settings are kept and that migration 0011 runs. Where to run them: - on a clean Windows PC or VM; - or in the CI `windows` job once a Windows runner is registered (`WINDOWS_RUNNER`). Owner action that unblocks part of this: run `Chronos-Setup-1.1.1.exe` on the development PC and approve UAC.
Alby96 added this to the Road to 1.0 project 2026-11-16 15:32:37 +01:00
Alby96 added the area/desktoparea/releaseenhancement labels 2026-11-16 16:57:46 +01:00
Sign in to join this conversation.