search

sobotka / olive

NLE video editor
GNU General Public License v3.0
2 stars 1 forks source link

[CI] AppVeyor fails due to "exceeding maximum allowed artifact storage size" #118

Closed itsmattkc closed 4 years ago

itsmattkc commented 4 years ago

Summary All master AppVeyor builds appear to be failing due to the following error message:

Maximum allowed artifact storage size of 50000 Mb will be exceeded.

While at first glance, this seems odd since Olive is not larger than 50GB (or 50Gb) in size, this appears to be actually referring overall artifact storage. That is, we actually commit so much that we've consumed 50GB of storage total on AppVeyor's servers. Good job, everyone.

Unfortunately AppVeyor apparently does not expose functionality to manually delete artifacts. According to this thread on their support forum, the solution appears to require contacting AppVeyor directly and they'll increase the maximum storage limit. Seems unnecessary considering the vast, vast majority of those artifacts are useless to us, but anyways that seems to be what we need to do.

sobotka commented 4 years ago

This is so dumb. No way to automatically delete expired builds? Time offset?

itsmattkc commented 4 years ago

Their "policy" auto-deletes after 6 months, but there seems to be no control over it and no way to manually delete old artifacts.

In theory we could just disable AppVeyor artifacts since we upload to GitHub Releases anyway? Not sure how people feel about that.

Simran-B commented 4 years ago

Would still be useful to have CI builds for PRs. Can you contact their support to ask for a shorter retention time? One month should be long enough.

Artifacts can be pushed from within the build script, so it would be possible to check some conditions like the commit message and only upload if it starts with "/CI" for instance. For master it can be skipped entirely because of the GitHub continuous release as you say.

Simran-B commented 4 years ago

Is this available to you Matt? Or is it only in their Enterprise version?

Screenshot_20200509-095242__01

itsmattkc commented 4 years ago

@Simran-B Doesn't look like it, these are the only options I get: image

Generally I'm leaning towards AppVeyor artifacts aren't necessary. They're only Windows builds which aren't useful for a lot of us, and PRs aren't particularly hard to compile/test once you have a development environment set up.

itsmattkc commented 4 years ago

I believe this is superseded by #126