JENKINS-16025 - Fixed issue where all files go to the root of the bucket.  Now we apply the relative path inside the bucket.
JENKINS-16025 (https://issues.jenkins-ci.org/browse/JENKINS-16025?page=com.atlassian.streams.streams-jira-plugin:activity-stream-issue-tab)
Fixed issue where all files ended up at the root of the bucket.  Now it applies the relative path to the bucket.
Added the ability to configure a proxy host and port for connecting to S3
Merge pull request #17 from dmbeer/master

Region Selection Support Added
[maven-release-plugin] prepare release s3-0.5
[maven-release-plugin] prepare for next development iteration
Merge branch 'master' of https://github.com/jenkinsci/s3-plugin

Conflicts:
	src/main/java/hudson/plugins/s3/S3BucketPublisher.java
	src/main/java/hudson/plugins/s3/S3Profile.java
fixed typo in function name
Merge branch 'master' of https://github.com/ckapp-bullhorn/s3-plugin

Conflicts:
	src/main/java/hudson/plugins/s3/S3BucketPublisher.java
	src/main/java/hudson/plugins/s3/S3Profile.java
Feature: upload from the slave

This feature when enabled in the build configuration, will let the plugin
to upload the objects directly from the slave, instead of proxying the
file contents to the master first.
This is very useful when the slaves are running in EC2, but the master
runs outside of EC2.

Signed-off-by: brice <brice@daysofwonder.com>
Feature: managed S3 artifacts

This feature when enabled in the build configuration ties the upload
artifacts to the given build.
This means the following features are enabled:
* artifacts are finger printed and linked to the build
* artifacts can be downloaded directly from the build page in the
S3 Artifact section
* artifacts are automatically deleted when the build is deleted
* the S3 Copy Artifact build step can be used to download artifacts from S3
automatically, helping build complex pipelines

When this setting is disabled, the previous behavior is available, and
the artfacts are not linked.

Signed-off-by: brice <brice@daysofwonder.com>
Feature: add configuration to upload or not on build failure

Since commit 7198ceea723d6ba6faa731aceae81c4befa8f965, the artifacts
are always uploaded. In a fully managed by Jenkins scenario this might
be counter-productive to upload artifacts when the build fails.
Thus checking this checkbox allow to retrieve the original behavior.

Signed-off-by: brice <brice@daysofwonder.com>
Merge pull request #19 from masterzen/feature/managed-s3-artifacts

Fully managed S3 artifacts and assorted changes
JENKINS-21594: Allow to upload file without wildcard

Commit 24a3b88[1] introduced a feature for wildcard uploads, but broke
the original behavior if your upload is configured with a straight
filename.

For instance:
Destination bucket: path/to/dir
Source: file.tar.gz

Would be uploaded as path/to/dir, missing completely the source file name.

This commit fixes this specific issue.

[1]
https://github.com/jenkinsci/s3-plugin/commit/24a3b88a7b9acb0532deabe686944e53747c49a9

Signed-off-by: Brice Figureau <brice@daysofwonder.com>
Merge pull request #21 from masterzen/fix/JENKINS-21594-no-wildcard-upload

JENKINS-21594: Allow to upload file without wildcard
Merge branch 'master' of github.com:thomshutt/s3-plugin