Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-60415

Deleting project does not delete artifacts from S3

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • Jenkins ver. 2.190.3, Artifact Manager on S3 plugin 1.7

      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.

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

          Jesse Glick added a comment -

          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.

          Jesse Glick added a comment - 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.

          Joe Barker added a comment -

          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.

           

          Joe Barker added a comment - 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.  

          Seeing the same problem with the a git multibranch pipeline. When a multibranch scan deletes a branch the artifacts for the branch get left behind on S3.

          Kent Sutherland added a comment - Seeing the same problem with the a git multibranch pipeline. When a multibranch scan deletes a branch the artifacts for the branch get left behind on S3.

          Facing the same issue! is there any solution/workaround for this ?

          walid boussafa added a comment - Facing the same issue! is there any solution/workaround for this ?

          Jesse Glick added a comment -

          Only to stop setting the unsupported system property, and instead configure time-based expiration (or move to Glacier) for all artifacts in the S3 bucket.

          Jesse Glick added a comment - Only to stop setting the unsupported system property, and instead configure time-based expiration (or move to Glacier) for all artifacts in the S3 bucket.

            Unassigned Unassigned
            lukelast Luke Last
            Votes:
            2 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: