Age | Commit message (Collapse) | Author | |
---|---|---|---|
2022-01-24 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2021-10-19 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-04-09 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-02-25 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-05-07 | Clean up CarrierWave's import/export files | Stan Hu | |
Unlike uploads that have been uploaded with Tempfile, the project import/export archives are stored in a temporary cache directory and remain there if: 1. Object storage is enabled 2. `move_to_store` is set to `true`. CarrierWave will leave these files there until disk space runs out or a clean step is run manually. If `move_to_store` is set to `false`, CarrierWave will remove the files after storing them. However, unlike a local file, with object storage, the file is still copied, so setting `move_to_store` to `true` doesn't buy us anything. To ensure files are cleaned up, we can just inherit from the GitlabUploader implementation of `move_to_store`, which returns `true` if it's a local file, `false` otherwise. Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/60656 | |||
2018-08-02 | Add Object Storage to GitLab project import | James Lopez | |
- Refactor uploads manager - Refactor importer, update import spec - Add more object storage specs | |||
2018-07-22 | Enable frozen string in newly added files | gfyoung | |
Enables frozen string for new files in directories that had been previously covered in previous MR's. Partially addresses #47424. | |||
2018-07-06 | Update Import/Export to use object storage (based on aa feature flag) | James Lopez | |