Consider having some DSL to store artifacts between steps #2301
Unanswered
x80486
asked this question in
Request a Feature
Replies: 1 comment
-
Steps share a workspace, so there should be no additional need to share artifacts between steps. For releases most forges provide a way to store artifacts. Only thing left I can image would be sth like test reports / screenshots from e2e tests etc. For those I would propose to use some plugin like an s3-uploader and use #1006 to show an url to the uploaded files in Woodpecker. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Clear and concise description of the problem
Pipelines do many things, but most of the times there is always a resultant artifact. This could be a release, some file(s) to be used by subsequent steps, and so on.
Woodpecker CI could be enhanced to allow storing these artifacts between steps.
Suggested solution
Alternative
N/A
Additional context
This could be also a way to persist some other files for doing reporting, code coverage reports, etc.
Validations
Beta Was this translation helpful? Give feedback.
All reactions