Error 500 in build worker API when artifacts storage size limit reached

[IlyaFinkelshteyn]

No description provided.

[austinv900]

Any update for this?

[IlyaFinkelshteyn]

Will try to fix it in next milestone. @austinv900 do you have account with this issue right now? Lest us know, we will unblock you by increasing the artifacts storage size limit.

[austinv900]

Yes I do. @IlyaFinkelshteyn What do you need from me?

[IlyaFinkelshteyn]

@austinv900 Link to failed build or just account name (part after project in URL).

[austinv900]

https://ci.appveyor.com/project/crackedgameservers/difftool

[IlyaFinkelshteyn]

Should be good now. Side question -- why you use GitHub repository as a generic Git? You are loosing a lot of nice features implemented by us using GitHub API...

[austinv900]

still kinda playing around with features. Been working with a dotnet core helper application for appveyor

[nyanhp]

Hi @IlyaFinkelshteyn , I think I have a related issue with https://ci.appveyor.com/project/AutomatedLab/automatedlab, which recently stopped pushing artifacts and the exception looks pretty much the same. We are using the PowerShell cmdlet Push-AppVeyorArtifact and it fails with code 500 as well. At the moment, this does not fail our build, but it might be that way in the future.
If necessary, I can open up another issue, but to me they seem related. If you guys need additional info, let me know.

[IlyaFinkelshteyn]

@nyanhp we just bumped your artifact storage limit so you should be good now. Sorry for the trouble.

[nyanhp]

Cool, thanks. Am I correct in assuming that there is no retention I can set yet to e.g. only have the artifacts of the last three builds?

[IlyaFinkelshteyn]

There are still not retention (it is coming), but we will increase your limit again if you hit it again. We were needed to add that limits to get some control over artifact storage and prevent obvious abuse, but we are OK to increase it for customers who need it.

[pcercuei]

We seem to get the same error here: https://ci.appveyor.com/project/pioneerspacesim/pioneer

The build succeeds but the artifact upload fails with (500) internal server error. I assume we're also hitting the artifact storage limit.

Upping the limit only delays the problem, is there a way to nuke all the artifacts older than a certain date?
Have it done automatically maybe? (e.g. nuke all the artifacts older than 10 days).

[IlyaFinkelshteyn]

@pcercuei Upping the limit is OK solution, because retention policy will start catch up with your artifact collection speed. We increased the limit for you, please do not hesitate to ping us again.

[pcercuei]

It works now. Thanks!

[pcercuei]

@IlyaFinkelshteyn, looks like we're hitting the limit again :(

[fluffyfreak]

@IlyaFinkelshteyn
Is there no way to remove old artifacts?
Or to configure how long they should be stored for?

We really only need them for the build itself, and maybe half a day afterwards, not the 6 months it's set too.

I tried cleaning out old builds but new builds are still failing and holding up a new deployment for us.

[FeodorFitsner]

@pcercuei it's been extended. Should be OK now.

@fluffyfreak what's your account name?

[fluffyfreak]

@FeodorFitsner it's ok, @pcercuei and I are on the same project.

Are there plans to allow us to delete old artifacts, or adjust the retention period?

[FeodorFitsner]

Sure, we are working on that.

[pcercuei]

We face the same problem once again :(
How much space do we use right now?

[fluffyfreak]

@FeodorFitsner we're facing this problem again, has there been any work/progress on allowing us to delete artefacts?

How do other teams handle this because we can't be the only team facing these issues?

[FeodorFitsner]

@fluffyfreak what's your AppVeyor account?

[fluffyfreak]

@FeodorFitsner https://ci.appveyor.com/project/pioneerspacesim/pioneer is where we're having the problem

[impaktor]

@FeodorFitsner hi! we (pioneerspacesim & @fluffyfreak above) still have failed build on all pull requests, it would be great if you could delete our old artefacts so it will work again, thanks!