org.jclouds.aws.AWSResponseException: request POST https:///?delete HTTP/1.1 failed with code 400, error: AWSError{requestId='', requestToken='', code='InvalidRequest', message='Invalid Request.'}
at org.jclouds.aws.handlers.ParseAWSErrorFromXmlContent.handleError(ParseAWSErrorFromXmlContent.java:76)
at org.jclouds.http.handlers.DelegatingErrorHandler.handleError(DelegatingErrorHandler.java:65)
at org.jclouds.http.internal.BaseHttpCommandExecutorService.shouldContinue(BaseHttpCommandExecutorService.java:138)
at org.jclouds.http.internal.BaseHttpCommandExecutorService.invoke(BaseHttpCommandExecutorService.java:107)
at org.jclouds.rest.internal.InvokeHttpMethod.invoke(InvokeHttpMethod.java:91)
at org.jclouds.rest.internal.InvokeHttpMethod.apply(InvokeHttpMethod.java:74)
at org.jclouds.rest.internal.InvokeHttpMethod.apply(InvokeHttpMethod.java:45)
at org.jclouds.rest.internal.DelegatesToInvocationFunction.handle(DelegatesToInvocationFunction.java:156)
at org.jclouds.rest.internal.DelegatesToInvocationFunction.invoke(DelegatesToInvocationFunction.java:123)
at com.sun.proxy.$Proxy201.deleteObjects(Unknown Source)
at org.jclouds.s3.blobstore.S3BlobStore.removeBlobs(S3BlobStore.java:341)
at io.jenkins.plugins.artifact_manager_jclouds.JCloudsVirtualFile.delete(JCloudsVirtualFile.java:375)
Caused: java.io.IOException
at io.jenkins.plugins.artifact_manager_jclouds.JCloudsVirtualFile.delete(JCloudsVirtualFile.java:379)
at io.jenkins.plugins.artifact_manager_jclouds.JCloudsArtifactManager.delete(JCloudsArtifactManager.java:213)
at hudson.model.Run.deleteArtifacts(Run.java:1613)
at org.jenkinsci.plugins.workflow.job.WorkflowRun.deleteArtifacts(WorkflowRun.java:684)
at hudson.tasks.LogRotator.perform(LogRotator.java:211)
We have noticed that when uploading artifacts to our custom s3 service endpoint that the artifacts are being deleted on our side but the Artifact Manager on S3 plugin is overriding our Build Discarder Plugin rules and preventing builds from being deleted. When using an s3 bucket directly, we are not facing these issues with the two plugins.
Originally reported by ewhitesell_nv, imported from: custom S3 service endpoint 400 deletion error
- status: Open
- priority: Minor
- component(s): artifact-manager-s3-plugin
- resolution: Unresolved
- votes: 0
- watchers: 2
- imported: 2025-12-02
Raw content of original issue
org.jclouds.aws.AWSResponseException: request POST https://<custom endpoint>/<jenkins instance>?delete HTTP/1.1 failed with code 400, error: AWSError{requestId='<request id>', requestToken='<request token>', code='InvalidRequest', message='Invalid Request.'}
at org.jclouds.aws.handlers.ParseAWSErrorFromXmlContent.handleError(ParseAWSErrorFromXmlContent.java:76)
at org.jclouds.http.handlers.DelegatingErrorHandler.handleError(DelegatingErrorHandler.java:65)
at org.jclouds.http.internal.BaseHttpCommandExecutorService.shouldContinue(BaseHttpCommandExecutorService.java:138)
at org.jclouds.http.internal.BaseHttpCommandExecutorService.invoke(BaseHttpCommandExecutorService.java:107)
at org.jclouds.rest.internal.InvokeHttpMethod.invoke(InvokeHttpMethod.java:91)
at org.jclouds.rest.internal.InvokeHttpMethod.apply(InvokeHttpMethod.java:74)
at org.jclouds.rest.internal.InvokeHttpMethod.apply(InvokeHttpMethod.java:45)
at org.jclouds.rest.internal.DelegatesToInvocationFunction.handle(DelegatesToInvocationFunction.java:156)
at org.jclouds.rest.internal.DelegatesToInvocationFunction.invoke(DelegatesToInvocationFunction.java:123)
at com.sun.proxy.$Proxy201.deleteObjects(Unknown Source)
at org.jclouds.s3.blobstore.S3BlobStore.removeBlobs(S3BlobStore.java:341)
at io.jenkins.plugins.artifact_manager_jclouds.JCloudsVirtualFile.delete(JCloudsVirtualFile.java:375)
Caused: java.io.IOException
at io.jenkins.plugins.artifact_manager_jclouds.JCloudsVirtualFile.delete(JCloudsVirtualFile.java:379)
at io.jenkins.plugins.artifact_manager_jclouds.JCloudsArtifactManager.delete(JCloudsArtifactManager.java:213)
at hudson.model.Run.deleteArtifacts(Run.java:1613)
at org.jenkinsci.plugins.workflow.job.WorkflowRun.deleteArtifacts(WorkflowRun.java:684)
at hudson.tasks.LogRotator.perform(LogRotator.java:211)
We have noticed that when uploading artifacts to our custom s3 service endpoint that the artifacts are being deleted on our side but the Artifact Manager on S3 plugin is overriding our Build Discarder Plugin rules and preventing builds from being deleted. When using an s3 bucket directly, we are not facing these issues with the two plugins.
- environment:
Jenkins 2.415, Build Discarder Plugin, Artifact Manager on S3
We have noticed that when uploading artifacts to our custom s3 service endpoint that the artifacts are being deleted on our side but the Artifact Manager on S3 plugin is overriding our Build Discarder Plugin rules and preventing builds from being deleted. When using an s3 bucket directly, we are not facing these issues with the two plugins.
Originally reported by ewhitesell_nv, imported from: custom S3 service endpoint 400 deletion error
Raw content of original issue
Jenkins 2.415, Build Discarder Plugin, Artifact Manager on S3