chore: Don't store video and screenshot artifacts for runs #20979
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
User facing changelog
N/A
Additional details
We're storing videos and screenshots within Circle that I don't believe anyone is utilizing in a meaningful way. We already upload screenshots and videos to the Cypress Dashboard where they could be viewed. This is taking up a bit of storage space in Circle which costs us some money. It's not a huge part of our bill, but seemed like a quick optimization.
The only time I can see the saving of these artifacts being useful in CircleCI is on runs that are not recorded to Cypress - so outside contributor PRs. I figure if these become really necessary to debug a failure within CI that the capturing of these artifacts could be added to the PR to look at the specific video/screenshot if necessary. It's also a bit random which jobs were keeping these and which weren't.