Jenkins setup: running the “jenkins/jenkins:2.462.3-jdk17” image in a K8s cluster
Hello,
we’re using s3Upload() provided by s3-plugin in our pipeline to upload some very large artifacts (70 GB) to S3. The upload (using managedArtifacts=true and uploadFromSlave=true) works fine, the files appear in S3 and also on this S3 Artifacts page in the build.
[Pipeline] stage
[Pipeline] { (Declarative: Post Actions)
[Pipeline] script
[Pipeline] {
[Pipeline] s3Upload
Publish artifacts to S3 Bucket Build is still running
Publish artifacts to S3 Bucket Using S3 profile: s3-artifacts
Publish artifacts to S3 Bucket bucket=dedicaid-jenkins-artifacts, file=dedicaid_onprem-master-56.7z region=eu-central-1, will be uploaded from slave=true managed=true , server encryption false
[Pipeline] }
[Pipeline] // script
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
The problem is that within hours of a successful build, the S3 Artifacts page disappears. Even adding /s3/ to the URL doesn’t work any more to show the page. The artifacts still exist in the bucket, but Jenkins forgets about them. There is no mention of any problems in Jenkins logs.
I browsed the plugin’s source code for clues, but all I could find was where the S3 page is being added, but I don’t know how this information is then persisted into build’s data and what to check for.
Can you kind help?