[JIRA] (JENKINS-44446) Content-Type not set correctly

2 views

Skip to first unread message

vineet.reynolds@gmail.com (JIRA)

unread,

Sep 1, 2019, 6:59:03 AM9/1/19

to jenkinsc...@googlegroups.com

Vineet Reynolds Pereira commented on

JENKINS-44446

Re: Content-Type not set correctly

Ran into a similar issue, when attempting to set 'Cache control' headers during publishing to S3, and eventually figured out that the userMetadata parameter had to be set twice (going by the Jenkins pipeline syntax editor). Oddly enough, it worked.

Working pipeline step is as follows:

 
                                                                step([$class: 'S3BucketPublisher',
 consoleLogLevel: 'INFO',
 dontWaitForConcurrentBuildCompletion: false,
 entries: [[
 bucket: 'example.com',
 excludedFile: '',
 flatten: false,
 gzipFiles: false,
 keepForever: false,
 managedArtifacts: false,
 noUploadOnFailure: true,
 selectedRegion: 'ap-south-1',
 showDirectlyInBrowser: false,
 sourceFile: 'dist/**/*',
 storageClass: 'STANDARD',
 uploadFromSlave: true,
 useServerSideEncryption: false,
 userMetadata: [[key: 'Cache-Control', value: 'max-age=86400']]
 ]],
 profileName: 's3deployer',
 pluginFailureResultConstraint: 'FAILURE',
 userMetadata: [[key: 'Cache-Control', value: 'max-age=86400']]
 ]) 
                                                            