Access to CI build folder

[DavidTNguyen]

Description

Many testing tools and frameworks like Cypress, JUnit, Spock, etc...can generates screenshots or small video clips that capture the steps leading to the runtime error. How can developers access that info on CI Server?

Value

It helped pin point the root cause of failure during integration or end-2-end testing. Having the exact reproducible steps with visual assistance allows developers troubleshoot and fix the bug faster.

Definition of Done

Users can navigate, view or download the artifacts for each build.

Effort (Optional)

Estimated effort to complete this story? (Best Guess e.g. 1-2 days)

Impacted Personas (Optional)

Which personas will benefit from completing this story? (Users, Administrators, etc)

[wass3r]

So, this is not really a UI problem (yet), but an architectural one. The build environment is tore down immediately after it finishes the build, and so is access to the build workspace and any intermediary files that were stored during the run of the build.

Typically, the solution has been to bring your own storage and introduce a step in your pipeline that sends off artifacts from the build workspace to said storage for later retrieval.

I know CI tools like Circle CI, GitHub Actions have built-in allotted storage for artifacts. Travis and Drone operate similarly to Vela where you are expected to provide your own storage solution (typically S3 buckets) and introduce a step or configure an add-on to offload artifacts to.

If you are intending to suggest a feature along the lines of the former scenario, we probably want to move this story elsewhere to start with.

[jbrockopp]

Hello 👋

The Vela admins have decided to condense all existing issues into a single repo found @ go-vela/community.

For a direct link to your counterpart issue in that repo, you can find it linked yesterday in the history of this issue.

If you have any questions, please feel free to direct them to the community repo.

Thanks for your input and feedback!