Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-28849

skip compressing already compressed artifacts

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      Sometimes an artifact will already be a zip file, and in this case it would be great to skip double-zipping it, especially as this makes it impossible to browse in the web view. We could add a step to unzip the artifact beforehand, however this causes the archiving step to take quite a while (1-3 minutes) as the compression appears to be done master-side so the whole directory has to be sent from slave to master before zipping.

        Attachments

          Activity

          Hide
          olivergondza Oliver Gondža added a comment -

          There is, DirectoryBrowserSupport in core can be improved to allow archive browsing. Then it would work in compress artifact plugin or any other artifact storage mechanism. It can even be used for workspace browsing and possibly other uses.

          Show
          olivergondza Oliver Gondža added a comment - There is, DirectoryBrowserSupport in core can be improved to allow archive browsing. Then it would work in compress artifact plugin or any other artifact storage mechanism. It can even be used for workspace browsing and possibly other uses.
          Hide
          mcrooney mcrooney added a comment -

          Okay, this is the change that makes a big usability difference for us, in terms of being able to browse the contents in the UI. What do you think? https://github.com/mrooney/compress-artifacts-plugin/commit/ff892755606aac0629fc9617e25d92da1df31532

          Show
          mcrooney mcrooney added a comment - Okay, this is the change that makes a big usability difference for us, in terms of being able to browse the contents in the UI. What do you think? https://github.com/mrooney/compress-artifacts-plugin/commit/ff892755606aac0629fc9617e25d92da1df31532
          Hide
          olivergondza Oliver Gondža added a comment -

          As I said this is really a matter of presentation, not storage. If you save X then you should get X when you download or copy artifacts to different build. This is not really a problem of compress artifact plugin as transparent compression is not supposed to modify the observed data.

          I am closing this issue and creating JENKINS-28852 to track your request. Make sure to watch it, I was not able to make you a reporter nor a watcher.

          Show
          olivergondza Oliver Gondža added a comment - As I said this is really a matter of presentation, not storage. If you save X then you should get X when you download or copy artifacts to different build. This is not really a problem of compress artifact plugin as transparent compression is not supposed to modify the observed data. I am closing this issue and creating JENKINS-28852 to track your request. Make sure to watch it, I was not able to make you a reporter nor a watcher.
          Hide
          mcrooney mcrooney added a comment -

          Thanks Oliver, I'll follow that issue and use our custom .hpi in the meantime. The issue is actually more than presentation though. The reason we compress a zip on the slave is because it takes 1-3 minutes for compress-artifacts to archive the directory from slave to master, and only about 3 seconds to archive a zipped version. The directory we are archiving is about 1.5GB with tons of files, so we zip it first on the slave and archive that as it goes down to 75MB. If the compress-artifacts compressed locally, that would also solve our problem.

          Show
          mcrooney mcrooney added a comment - Thanks Oliver, I'll follow that issue and use our custom .hpi in the meantime. The issue is actually more than presentation though. The reason we compress a zip on the slave is because it takes 1-3 minutes for compress-artifacts to archive the directory from slave to master, and only about 3 seconds to archive a zipped version. The directory we are archiving is about 1.5GB with tons of files, so we zip it first on the slave and archive that as it goes down to 75MB. If the compress-artifacts compressed locally, that would also solve our problem.
          Hide
          olivergondza Oliver Gondža added a comment -

          Unfortunately, console tools will always be faster that Java implementation we use. However, you are right there might be a way to optimize the archiving process: JENKINS-28862.

          Show
          olivergondza Oliver Gondža added a comment - Unfortunately, console tools will always be faster that Java implementation we use. However, you are right there might be a way to optimize the archiving process: JENKINS-28862 .

            People

            • Assignee:
              olivergondza Oliver Gondža
              Reporter:
              mcrooney mcrooney
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: