New version: JetBrains.YouTrack version 24.3.56671
/AzurePipelines run
@wingetbot run
/AzurePipelines run
/AzurePipelines run
/AzurePipelines run
@wingetbot run
/AzurePipelines run
/AzurePipelines run
/AzurePipelines run
/AzurePipelines run
=== manifests\j\JetBrains\YouTrack\24.3.56671 === Missing Properties value based on version 23.1.16998: Scope UpgradeBehavior Switches AppsAndFeaturesEntries
Hi @SpecterShell,
Are these properties significant, or are they intentionally omitted?
=== manifests\j\JetBrains\YouTrack\24.3.56671 === Missing Properties value based on version 23.1.16998: Scope UpgradeBehavior Switches AppsAndFeaturesEntries
Automatic Validation ended with:
Installation failed with exit code -1978335226 2025-01-16 19:07:37.167 [CLI ] ShellExecute installer failed: 1603 MSI (s) (58:3C) [19:07:36:316]: Product: Bluebeam Revu x64 21 -- Disk full: Out of disk space -- Volume: 'C:'; required space: 3,373,021 KB; available space: 1,951,332 KB. Free some disk space and retry. Disk full: Out of disk space -- Volume: 'C:'; required space: 3,373,021 KB; available space: 1,951,332 KB. Free some disk space and retry. Property(S): PrimaryVolumeSpaceRemaining = 0 Property(S): PrimaryVolumeSpaceRequired = 0 Property(S): PrimaryVolumeSpaceAvailable = 0 Property(S): OutOfNoRbDiskSpace = 1 Property(S): OutOfDiskSpace = 1 Property(S): ErrorDialog = SetupError MSI (s) (58:3C) [19:07:36:707]: Product: Bluebeam Revu x64 21 -- Installation operation failed.
Automated error analysis suggests -1978335226 may mean Running ShellExecute failed
Automated error analysis suggests 1603 may mean Previous MSI installer is missing (Or it might mean Install successful but system restart may be required.) Should this be add as an InstallerSuccessCode or similar?
(Automated response - build 942.)
Edit: This seems relevant:
MSI (s) (58:3C) [19:07:36:316]: Product: Bluebeam Revu x64 21 -- Disk full: Out of disk space -- Volume: 'C:'; required space: 3,373,021 KB; available space: 1,951,332 KB. Free some disk space and retry.
Publish pipeline succeeded for this Pull Request. Once you refresh your index, this change should be present.