Consider having some DSL to store artifacts between steps

[x80486]

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.

Notice this could look like a cache, but it's intended for something completely different.

Suggested solution

pipeline:
  assemble:
    artifacts:
      expire_in: 1 year # 3 months, 7 days, 1 week
      paths:
        - ${CI_PROJECT_DIR}/target/
    ...

Alternative

N/A

Additional context

This could be also a way to persist some other files for doing reporting, code coverage reports, etc.

Validations

• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

[anbraten]

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.