populate select from descriptor, or they get empty when a new entry is created
Make S3 signed URL expiry configurable, with 60s default

Per JENKINS-23897, S3 signed URLs for downloads were very sensitive to server
clock drift / time sync issues. The hardcoded 4 second expiry was too short even
if the server time was accurate if Jenkins took a moment to respond and/or
the request to S3 took a moment. On high latency links like 3G downloads frequently
failed.

Make the timeout configurable under Advanced, and default to 60 seconds instead
of 4.
Merge pull request #31 from ndeloof/master

populate select from descriptor, or they get empty when a new entry is created
Merged changes
Merge branch 'recampbell-jenkins-19587'
Revert "Merge branch 'recampbell-jenkins-19587'"

This reverts commit a5384f10dad6a76c79995ac426feda84e08c9f8b, reversing
changes made to 9fac76f226b75f5224a42c3651a4ad107da10f46.
[JENKINS-25668] Use Jenkins data binding
using custom parameter prefix result in multiple use of s3 publisher in distinct promotions to be captured as actions for all promotions.
forgot to rename help file
unlatching attribute name
prevent possible NPE
AbstractDescribableImpl refer to Jenkins class and prevent removability for this data class
Update AWS SDK to 1.9.6

This version is needed for EU_CENTRAL_1 region to be included.
Merge pull request #33 from ringerc/longer-url-expiry

Make S3 signed URL expiry configurable, with 60s default
Merge pull request #41 from wilgert/master

Update AWS SDK to 1.9.6
Allow S3 upload retry logic to function by draining remote to file

For local files, just grab the file name out of the path (poorly-named
getRemote()).

For remote files drain the file over the remoting channel over to a
tempfile on the master, then pass that tempfile into the client, then
delete the file in the finally block.

This allows AmazonS3Client's built in 'ResettableFileInputStream' to
kick in, which it does not when you directly pass a stream in the upload
request.

This only matters when proxying the upload through the master. All other
times, the file really exists on disk and the input stream is a normal
FileInputStream.
Merge pull request #29 from schrodinger/upload-via-filename

Upload files via filename to AmazonS3Client
[maven-release-plugin] prepare release s3-0.7
[maven-release-plugin] prepare for next development iteration
Merge jenkinsci/master into mediaplayout/http-headers