Large archives negatively impact stash performance

[Former user]

Can we introduce a feature to prevent the creation of an archive over a certain size?

We have some large repositories (> 1 GB) which introduce significant performance hits when attempting to archive them (See attached)

[Bryan Turner]

The archive plugin uses an "scm-hosting" ticket, like a push or pull, to try and gate its performance hit. However, the actual performance is down to Git itself.

Newer versions of the plugin allow administrators to configure the maximum duration archive processes are allowed to run. However, there's not really any way to introduce limits based on size because the system doesn't know how large an archive is going to be until it creates it. ("git archive" has no flags to try and limit sizes.)

plugin.bitbucket-archive.timeout.execution can be used to control the process timeout. The value is defined in seconds, so 120 means 2 minutes. The default is half an hour.