An error occurred fetching the project authors.
- 05 Jun, 2018 1 commit
-
-
Jacob Vosmaer (GitLab) authored
-
- 24 May, 2018 1 commit
-
-
Stan Hu authored
-
- 15 Jan, 2018 2 commits
-
-
Balasankar "Balu" C authored
-
Balasankar "Balu" C authored
-
- 22 Oct, 2017 1 commit
-
-
Maxim Rydkin authored
-
- 21 Oct, 2017 1 commit
-
-
Rémy Coutable authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-
- 18 Oct, 2017 1 commit
-
-
Rémy Coutable authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-
- 21 Sep, 2017 1 commit
-
-
Tiago Botelho authored
-
- 20 Sep, 2017 1 commit
-
-
Tiago Botelho authored
-
- 09 Aug, 2017 1 commit
-
-
Rémy Coutable authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-
- 27 Jul, 2017 1 commit
-
-
Markus Koller authored
-
- 23 May, 2017 2 commits
-
-
Achilleas Pipinellis authored
-
Achilleas Pipinellis authored
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/10901/diffs introduced a new naming scheme for backups, but the code which cleans up old backups wasn't updated accordingly. In order to maintain backward compatibility, we need to account for 3 naming schemes.
-
- 26 Apr, 2017 1 commit
-
-
Maxim Rydkin authored
-
- 25 Apr, 2017 1 commit
-
-
Achilleas Pipinellis authored
Instead of doing hacks like http://stackoverflow.com/a/26082612/974710
-
- 28 Feb, 2017 1 commit
-
-
Jon Keys authored
-
- 23 Feb, 2017 1 commit
-
-
Douwe Maan authored
-
- 31 Jan, 2017 1 commit
-
-
Kamil Trzcinski authored
-
- 09 Jan, 2017 1 commit
-
-
Adam Niedzielski authored
-
- 07 Dec, 2016 1 commit
-
-
Sean McGivern authored
-
- 30 Nov, 2016 1 commit
-
-
David Gerő authored
-
- 11 Aug, 2016 1 commit
-
-
bogdanvlviv authored
Since version ruby-2.2.0, method `File::exists?` is deprecated.
-
- 10 Jun, 2016 1 commit
-
-
Stan Hu authored
Closes #12710
-
- 03 Jun, 2016 3 commits
-
-
Connor Shea authored
Colorize is a gem licensed under the GPLv2, so we can’t use it in GitLab without relicensing GitLab under the terms of the GPL. Rainbow is licensed under the MIT license and does the exact same thing as Colorize, so Rainbow was added in place of Colorize. The syntax is slightly different for Rainbow vs. Colorize, and was updated in accordance. The gem is still a dependency of Spinach, so it’s included in the development/test environments, but won’t be packaged with the actual product, and therefore doesn’t require we relicense the product. An attempt at relicensing Colorize was made, but didn’t succeed as the library owner never responded. Rainbow library: https://github.com/sickill/rainbow Relevant issue regarding licensing in GitLab's gems: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/3775
-
James Lopez authored
This reverts commit 3e991230.
-
James Lopez authored
# Conflicts: # app/models/project.rb
-
- 31 May, 2016 1 commit
-
-
Robert Speicher authored
This is idempotent, so there's no harm calling it if the directory already exists. Closes #12710
-
- 25 May, 2016 1 commit
-
-
Kamil Trzcinski authored
-
- 23 May, 2016 1 commit
-
-
Kamil Trzcinski authored
-
- 16 May, 2016 1 commit
-
-
Kamil Trzcinski authored
-
- 08 Feb, 2016 1 commit
-
-
Jeroen Nijhof authored
-
- 19 Nov, 2015 1 commit
-
-
Marin Jankovski authored
-
- 18 Nov, 2015 2 commits
-
-
Marin Jankovski authored
-
Marin Jankovski authored
-
- 10 Nov, 2015 1 commit
-
-
Kamil Trzcinski authored
- Offloads uploading to GitLab Workhorse - Use /authorize request for fast uploading - Added backup recipes for artifacts - Support download acceleration using X-Sendfile
-
- 06 Oct, 2015 3 commits
-
-
Jacob Vosmaer authored
Documentation elsewhere refers to this internal path, let's keep it.
-
Jacob Vosmaer authored
By using light gzip compression we can save a lot of disk IO during the backup.
-
Jacob Vosmaer authored
During the backup we create an intermediate copy of two directories: builds and uploads. Instead of creating many small files with 'cp -r', we now use tar (and fast gzip) to create single intermediate files. This saves on disk IO and disk space while creating a backup.
-
- 25 Sep, 2015 1 commit
-
-
Paul Beattie authored
This adds support for AWS S3 SSE with S3 managed keys, this means the data is encrypted at rest and the encryption is handled transparently to the end user as well as in the AWS Console. This is optional and not required to make S3 uploads work.
-
- 15 Sep, 2015 1 commit
-
-
Kamil Trzcinski authored
-