Fedor Korotkov

I think it might be handy to mark some of [Cirrus artifacts](https://cirrus-ci.org/guide/writing-tasks/#artifacts-instruction) as GitHub Release artifacts and re-upload them to GitHub as well. Something like: ```yaml binary_artifacts: path: "build/bin/*" github_asset:...

Might be a good use case for Starlark: https://cirrus-ci.org/guide/programming-tasks/

It's due to the number of files. Cirrus doesn't zip the artifacts first and unzips on the server side. Instead it uses a single GRPC stream to stream all files...

Batch upload is not supported and only batch updates/deletes/etc. Compressing won't work since you'll still need to decompress and create 1000s of files. And storing just the compressed archive won't...

Closing since there is nothing can be done. FYI the uploads became much faster since the time of the issue creation so it might be not as notable nowadays.

Will be achieved with Starlark as part of #1078

I don't see Stackdriver integration with statuspage.io. I was thinking about simply creating a static page and share a few charts from Stackdriver. Luckly Stackdriver allows to publicly share charts...

Since now Cirrus has Charts in GraphQL API we can easily expose some status graphs (#326). I wonder which one... - Average queue time of tasks - Amount of scheduled...

Is it a privileged/KVM-enabled container?

Got it. Yeah, because it's starting in a separate VM we don't have that much visibility if startup script failed. Changed the description.