Artifacts exceeded limits

[craig-dae]

We just started getting Cannot upload artifacts. You may have exceeded your spending limit for storing artifacts with Actions or Packages.

We have an artifact that takes about 5 minutes to produce, which is fed into a job that spins up multiple containers than run in parallel. The artifacts are only needed to feed these boxes, and can be removed after.

After 1 day, we started getting the message I wrote above. I have deleted every artifact I could find manually. Then I ran this action here that says it purged all my artifacts: https://github.com/kolpav/purge-artifacts-action

Clicking through as many previous workflows as I could, I found no examples of existing artifacts.

I continue to the get above message, and all merging has stopped on our project.

I need to know how to manage my artifacts so this doesn't happen again, and get my pipeline back up asap.

Thanks!

[MJomaa]

Was the same here. You need to wait a few hours until they get purged. Seems like GitHub scans the storage space periodically.

[yacaovsnc]

Is this still an issue?

[craig-dae]

@yacaovsnc Thanks for getting back to me. I solved this by using kolpav/purge-artifacts-action@v1

      - name: Clear artifacts
        uses: kolpav/purge-artifacts-action@v1
        with:
          token: ${{ secrets.GITHUB_TOKEN }}
          expire-in: 1hr

This seems to keep my artifacts in check. Has this issue been fixed? Can I remove kolpav/purge-artifacts-action@v1 or do I need to keep it in?

[dig]

Would be nice if we could define expire-in for upload-artifact. I've solved this by using kolpav/purge-artifacts-action@v1 for now.

[craig-dae]

I, personally, would prefer some kind of FIFO for artifacts. Maybe specify an optional limit for a pipeline, in case you have multiple pipelines. Once you hit the limit for a specific pipeline, it starts deleting old artifacts.

In my pipeline, I have one action to build an artifact, and a second set of parallel actions to consume it. After that, the artifact has no value anymore, unless I'm debugging an issue that requires me to download the artifact and inspect it. 99% of the time, artifacts outlive their usefulness within a few seconds of being created.

[ahdbilal]

You can now change artifact and log retention duration either through Actions Settings tab or via YAML. You can learn more about this feature here. Feedback is welcome!

[ThiefMaster]

@ahdbilal Would it be possible to have retention periods below one day? For the Passing data between jobs in a workflow usecase a few minutes would be more than enough, or even better a "until run finished" retention where the artifact gets deleted immediately after the job finished.

[typelogic]

Use the retention-days: 2 in actions/upload-artifact@v1 so there is no more need to do any deletion

[ankush-custiv]

I have purged all my artifacts using olpav/purge-artifacts-action@v1 (github api gives artifact count as 0), still getting the same error and hence my workflow is blocked. Anyone else faced this ?

[StephenHodgson]

I'm wondering if upload artifact could just work like the cache, where it will delete the oldest instead of preventing the upload of a new artifact.

I also ran into this and manually deleted everything but kept getting this error for days after.

[p0358]

I'm wondering if upload artifact could just work like the cache, where it will delete the oldest instead of preventing the upload of a new artifact.

Though such feature should probably be opt-in to not catch people off-guard, and also per-repo, so it doesn't delete for example latest artifact from another repo that you might still need