agola/internal
Simone Gotti 34cfdfeb3b objectstorage: add size option to WriteObject
On s3 limit the max object size to 1GiB when the size is not provided (-1) or
the minio client will calculate a big part size since it tries to use the
maximum object size (5TiB) and will allocate a very big buffer in ram. Also
leave as commented out the previous hack that was firstly creating the file
locally to calculate the size and then put it (for future reference).
2019-05-02 09:47:38 +02:00
..
common *: rename "lts" to "ost" 2019-04-27 15:16:48 +02:00
config runservice: update docker registry auth 2019-04-22 14:38:25 +02:00
datamanager objectstorage: add size option to WriteObject 2019-05-02 09:47:38 +02:00
db Add database helper 2019-02-21 16:05:54 +01:00
etcd etcd: allow specifying a revision for a get 2019-03-29 11:37:22 +01:00
git-handler Add custom git server 2019-02-21 16:03:17 +01:00
git-save Add user local runs feature 2019-02-21 23:01:17 +01:00
gitsources gateway: use agola ID in gitsource tokenname 2019-04-30 12:13:12 +02:00
log Add common logging helper 2019-02-21 16:05:35 +01:00
objectstorage objectstorage: add size option to WriteObject 2019-05-02 09:47:38 +02:00
runconfig runservice: update docker registry auth 2019-04-22 14:38:25 +02:00
sequence etcd: allow specifying a revision for a get 2019-03-29 11:37:22 +01:00
services objectstorage: add size option to WriteObject 2019-05-02 09:47:38 +02:00
testutil etcd: allow specifying a revision for a get 2019-03-29 11:37:22 +01:00
toolbox toolbox: initial commit 2019-02-21 15:57:11 +01:00
util util: add path functions 2019-04-30 16:24:04 +02:00
tools.go Add makefile 2019-02-21 15:59:16 +01:00