iModelBridges folder is not cleaned-up after update

Hi,

iTwinSychronizer 1.0.112 installed.

The problem is that it seems iModelBridges folder (C:\Users\<used>\AppData\Local\imodelbridges\) is not cleaned after a bridge updates, so just a few days after installation, the folder is 14 GB big for only 2 (MStn and Civil) bridges installed. There is a lot of trash inside the folder:

  • Different versions of .IModelBridgeForMstn-a.b.c.d
  • Folder .staging is full of zip files

Is it now some standard in Bentley that downloaded, temporary and not used files are not removed? E.g. CONNECTION client does the same (and it's the reason it's completely the garbage when treated as software automatic upgrade tool).

With regards,

  Jan

Parents
  • Each time you run a synchronization (e.g. click 'Synchronize'), it should clean up the imodelbridges directory (up to once per hour). I just saw this happen when I ran a job locally, but I'll also ask our QA team to try to reproduce. The cleanup will delete the entire .staging directory, and any old bridge versions still sitting in the imodelbridges directory. If you peek at the logs (%LOCALAPPDATA%Bentley\Logs\iTwinSynchronizer.log), you should see entries for iTwinSynchronizer.BridgeMaintenance indicating it's processing.

Reply
  • Each time you run a synchronization (e.g. click 'Synchronize'), it should clean up the imodelbridges directory (up to once per hour). I just saw this happen when I ran a job locally, but I'll also ask our QA team to try to reproduce. The cleanup will delete the entire .staging directory, and any old bridge versions still sitting in the imodelbridges directory. If you peek at the logs (%LOCALAPPDATA%Bentley\Logs\iTwinSynchronizer.log), you should see entries for iTwinSynchronizer.BridgeMaintenance indicating it's processing.

Children