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

Add option to save bandwidth and resources, which are wasted unnecessarily

      At this moment, the plugin always sends full build artifacts (tons of media files and etc) over each build, which is an absolute overkill and waste of:

      • resources & performance of Jenkins environment
      • resources & performance of staging/production site 

      so, whenever you have a chance, please implement this trivial things - before sending the artifact files, compare them to last sent file's md5 (or whatever) signature, and if content is not changed, don't resend. You can leave that 'option' by default turned off, but at least, give us way to enable that option.

          [JENKINS-67963] Add option to save bandwidth and resources, which are wasted unnecessarily

          For your information, all publish-over-ssh component type JENKINS issues related to the Publish Over SSH plugin have been transferred to Github: https://github.com/jenkinsci/publish-over-ssh-plugin/issues

          Here is the direct link to this issue in Github: https://github.com/jenkinsci/publish-over-ssh-plugin/issues/65
          And here is the link to a search for related issues: https://github.com/jenkinsci/publish-over-ssh-plugin/issues?q=%22JENKINS-67963%22

          (Note: this is an automated bulk comment)

          Gavin McDonald added a comment - For your information, all publish-over-ssh component type JENKINS issues related to the Publish Over SSH plugin have been transferred to Github: https://github.com/jenkinsci/publish-over-ssh-plugin/issues Here is the direct link to this issue in Github: https://github.com/jenkinsci/publish-over-ssh-plugin/issues/65 And here is the link to a search for related issues: https://github.com/jenkinsci/publish-over-ssh-plugin/issues?q=%22JENKINS-67963%22 (Note: this is an automated bulk comment)

          Closing ticket, please use the corresponding Github Issue as linked above.

          Gavin McDonald added a comment - Closing ticket, please use the corresponding Github Issue as linked above.

          s m added a comment -

          gmcdonald I have got notifications - if you can, please close the issue on github too, as someone has addressed that issue and waits for bounty. I can't close the topic there.

          s m added a comment - gmcdonald I have got notifications - if you can, please close the issue on github too, as someone has addressed that issue and waits for bounty. I can't close the topic there.

            Unassigned Unassigned
            selnomeria s m
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: