Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

delete the base64 file after job completes #49

Open
XinfinityoO opened this issue May 9, 2021 · 3 comments
Open

delete the base64 file after job completes #49

XinfinityoO opened this issue May 9, 2021 · 3 comments
Labels
documentation Improvements or additions to documentation

Comments

@XinfinityoO
Copy link

Hi
Is there anyway to delete the uploaded base64 file after the job is complete. AT the moment if you go to parameters under the specific build, you can download the uploaded file.

Thanks

@jglick
Copy link
Member

jglick commented May 27, 2021

If you use the stashed file parameter type, then you are using the behavior of stashes:

  • deleted at the end of the build by default for Scripted
    • unless you are using checkpoint in CloudBees CI
  • (IIRC) deleted after a few builds for Declarative, but not immediately, so you can restart failed stages
  • never deleted by default when using the artifact-manager-s3 plugin, unless you configure some policy in S3 itself

This could become a documentation PR if the behavior is verified experimentally.

@XinfinityoO
Copy link
Author

Hi
IS it possible to delete the uploaded stashedfile in a declarative pipeline, in the post build section? if so, could you let me know how this can be achieved.

Thanks

@jglick
Copy link
Member

jglick commented Jun 3, 2021

No, they just get deleted automatically after a few builds.

@jglick jglick added the documentation Improvements or additions to documentation label Mar 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

2 participants