[JIRA] (JENKINS-60415) Deleting project does not delete artifacts from S3

[luke@lukelast.com (JIRA)]

Luke Last created an issue

Jenkins / JENKINS-60415 Deleting project does not delete artifacts from S3 Issue Type: Bug Assignee: Unassigned Components: artifact-manager-s3-plugin Created: 2019-12-10 04:40 Environment: Jenkins ver. 2.190.3, Artifact Manager on S3 plugin 1.7 Priority: Major Reporter: Luke Last Note that I have the "-Dio.jenkins.plugins.artifact_manager_jclouds.s3.S3BlobStoreConfig.deleteArtifacts=true" value set. If I delete a single build then the corresponding artifacts are deleted from S3. If I delete the whole project then none of the artifacts are deleted in S3. Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)

[jglick@cloudbees.com (JIRA)]

Jesse Glick commented on JENKINS-60415

Re: Deleting project does not delete artifacts from S3 Could be considered a core bug in that JCloudsArtifactManager.delete ought to have been called for all the builds, but that would be inefficient anyway.

Add Comment

[joeb.uk@gmail.com (JIRA)]

Joe Barker commented on JENKINS-60415

Re: Deleting project does not delete artifacts from S3

This is also something that's impacting us. We're using the Bitbucket Branch Source plugin, and if any of our developers delete a branch from Bitbucket then Jenkins correctly removes the branch but any artifacts would remain in S3. Deleting a build through Jenkins does correctly remove the artifacts from S3, however.

Add Comment