Now that GitHub has a strict quota and charges on storage usage, the ability to remove artifacts is an essential feature. This is covered in #5, however, since Actions are automated, manual removal is too tedious.
I'd like to suggest supporting retention policies instead where after a period of time (specified in the job step), artifacts automatically clear themselves out to avoid wasting storage space.
For example, when sharing artifacts between jobs, they're only needed for an hour maximum, and for debugging tests they may not be needed for more than a day.
Here is a configuration example where expires is the retention policy given in seconds.
- uses: actions/upload-artifact@v1
with:
name: my-artifact-for-one-hour
path: path/to/artifact
expires: 3600
- uses: actions/upload-artifact@v1
with:
name: my-artifact-for-one-day
path: path/to/another/artifact
expires: 86400
Without this, the entire idea of "Shared Storage" in GitHub Actions is unusable for Teams and Individuals with fixed budgets as the costs will just keep growing.
#5 will still be needed to remove artifacts that don't have a retention policy.
Now that GitHub has a strict quota and charges on storage usage, the ability to remove artifacts is an essential feature. This is covered in #5, however, since Actions are automated, manual removal is too tedious.
I'd like to suggest supporting retention policies instead where after a period of time (specified in the job step), artifacts automatically clear themselves out to avoid wasting storage space.
For example, when sharing artifacts between jobs, they're only needed for an hour maximum, and for debugging tests they may not be needed for more than a day.
Here is a configuration example where
expiresis the retention policy given in seconds.Without this, the entire idea of "Shared Storage" in GitHub Actions is unusable for Teams and Individuals with fixed budgets as the costs will just keep growing.
#5 will still be needed to remove artifacts that don't have a retention policy.