Goal

There are certain types of artifacts that needs to be stored after a PipelineRun or a TaskRun has completed. These are artifacts that are usually associated with the Run that may need to be analyzed/displayed by other tools.

Examples of such artifacts are 

• Log files
• Test results, failures, and screenshots
• Stress test performance output and code coverage results
• Linter results

As a developer, I want to access and view the artifacts (test reports, summaries, videos, etc) generated within a PipelineRun after a run is completed so that I can review the outcome of pipeline execution for my application.

Note

• Upload: some of the alternates that was discussed an upload task or a sidecar for uploading given artifacts from a workspace. 
  *Storage: it should be able to define storage backend, also a global retention period. It is possible that we will also implement an API to access the files. 
  *Integrations: Console should be able to access and retrieve these artifacts related to a PipelineRun/TaskRun. The same access restrictions for the TaskRun/PipelineRun should apply to the artifacts.

Acceptance Criteria

• A pipeline author can specify to record artifacts such as test results, reports, summaries, videos, etc that are created through a PipelineRun
• The recorded artifacts are accessible to a developer who has access to a completed pipelinerun
• Admin can specify the storage backend for storing the artifacts: AWS, Azure and OSD
• Admin can specify the retention policy for pipelinerun artifacts