Uploaded image for project: 'Qt Quality Assurance Infrastructure'
  1. Qt Quality Assurance Infrastructure
  2. QTQAINFRA-3639

Mount CI's Storage as read-only storage for real-bug (ReleaseExport machine)

    XMLWordPrintable

Details

    • Task
    • Resolution: Done
    • P2: Important
    • None
    • None
    • Coin (obsolete)
    • None

    Description

      Now every registered (by ExportTool) integration is tar'ed and copied to real-bug where the tar package is extracted again so that ReleaseExport can produce final releasable content. This approach has the folloing cons:

      • Coin master resources are wasted to pack the .tar and disk space temporarily which is roughly 50G-60G per integration
      • Network bandwidth is consumed to transfer the 50G-60G per registered integration to real-bug
      • real-bug needs to unpack the tar
      • in effect there are 2 duplicates of each (tqtc-)qt5, 3dstudio, qtcreator, etc. integrations which is about 100++G per integration which quickly eats disk space from the compellent
      • transferring each tar'ed integration to real-bug also takes some time

      Proposal:

      mount the Coin's storage as read-only storage for real-bug machine

      Possible cons:

      • garbage collector, a new integration is started which the ReleaseExport still depends on (export ongoing) and the GC starts cleaning this integration away from storage?
      • Coin reboots -> storage disappears from ReleaseExport in the middle of the export?

      Attachments

        Activity

          People

            tosaraja Tony Sarajärvi
            iknd Iikka Eklund
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: