- 21 Mar, 2017 3 commits
-
-
Mike Greiling authored
-
Jacob Vosmaer authored
This helps you understand why the command failed.
-
Jacob Vosmaer authored
-
- 16 Mar, 2017 1 commit
-
-
Z.J. van de Weg authored
-
- 08 Mar, 2017 1 commit
-
-
Douwe Maan authored
-
- 03 Mar, 2017 1 commit
-
-
Alejandro Rodríguez authored
This will be necessary when adding gitaly settings. This version doesn't make any functional changes, but allows us to include this breaking change in 9.0 and add the needed extra settings in the future with backwards compatibility
-
- 28 Feb, 2017 1 commit
-
- 23 Feb, 2017 2 commits
-
-
Douwe Maan authored
-
Douwe Maan authored
-
- 21 Feb, 2017 1 commit
-
-
Gabriel Mazetto authored
-
- 16 Feb, 2017 1 commit
-
-
Mike Greiling authored
-
- 07 Feb, 2017 1 commit
-
-
Connor Shea authored
Cherry-picked 'Remove colorize methods that weren't in CE.'
-
- 03 Feb, 2017 1 commit
-
-
Adam Pahlevi authored
add complete changelog for !8949
-
- 31 Jan, 2017 2 commits
-
-
Kamil Trzcinski authored
- The pages are created when build artifacts for `pages` job are uploaded - Pages serve the content under: http://group.pages.domain.com/project - Pages can be used to serve the group page, special project named as host: group.pages.domain.com - User can provide own 403 and 404 error pages by creating 403.html and 404.html in group page project - Pages can be explicitly removed from the project by clicking Remove Pages in Project Settings - The size of pages is limited by Application Setting: max pages size, which limits the maximum size of unpacked archive (default: 100MB) - The public/ is extracted from artifacts and content is served as static pages - Pages asynchronous worker use `dd` to limit the unpacked tar size - Pages needs to be explicitly enabled and domain needs to be specified in gitlab.yml - Pages are part of backups - Pages notify the deployment status using Commit Status API - Pages use a new sidekiq queue: pages - Pages use a separate nginx config which needs to be explicitly added
-
Rémy Coutable authored
It's either ProjectCacheWorker#perform or ProjectCacheWorker.perform_async! Signed-off-by: Rémy Coutable <remy@rymai.me>
-
- 28 Jan, 2017 1 commit
-
-
Mike Greiling authored
-
- 27 Jan, 2017 1 commit
-
-
Mike Greiling authored
-
- 25 Jan, 2017 1 commit
-
-
Chris Wilson authored
-
- 10 Jan, 2017 3 commits
-
-
Mike Greiling authored
-
Luke "Jared" Bennett authored
-
Adam Niedzielski authored
-
- 05 Jan, 2017 1 commit
-
-
Robert Schilling authored
-
- 21 Dec, 2016 2 commits
-
-
Markus Koller authored
This adds counters for build artifacts and LFS objects, and moves the preexisting repository_size and commit_count from the projects table into a new project_statistics table. The counters are displayed in the administration area for projects and groups, and also available through the API for admins (on */all) and normal users (on */owned) The statistics are updated through ProjectCacheWorker, which can now do more granular updates with the new :statistics argument.
-
Markus Koller authored
-
- 16 Dec, 2016 1 commit
-
-
Drew Blessing authored
Sometimes admins will change the LDAP configuration, not realizing that problems will occur if the user's LDAP identities are not also updated to use the new provider name. This task will give admins a single command to run to update identities and will prevent having to run multiple Rails console queries.
-
- 01 Dec, 2016 1 commit
-
-
Rémy Coutable authored
The task will use the canonical repo and the required version. Signed-off-by: Rémy Coutable <remy@rymai.me>
-
- 30 Nov, 2016 3 commits
-
-
Rémy Coutable authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-
Rémy Coutable authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-
Rémy Coutable authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-
- 18 Nov, 2016 1 commit
-
-
Z.J. van de Weg authored
In the 8.13 RC cycle, so before the release, there was a time in which references in git where stored by id instead of iid. This could be fixed by time, if the iid catches up with the id, it overwrites it. But in the mean time we have wrong refs in the folder. This commit fixes that. For all projects we have deployments we'll find the ones where the ref has a higher number than the iid is now and calls `#create_ref` on the corresponding deployment.
-
- 17 Nov, 2016 1 commit
-
-
Rémy Coutable authored
This will prevent the task to advertise using https://gitlab-ci-token:xxxxxxxxxxxxxxxxxxxx@gitlab.com/gitlab-org/gitlab-ce.git when https://gitlab.com/gitlab-org/gitlab-ce.git is enough Signed-off-by: Rémy Coutable <remy@rymai.me>
-
- 10 Nov, 2016 1 commit
-
-
Rémy Coutable authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-
- 08 Nov, 2016 1 commit
-
-
Drew Blessing authored
It was previously possible for invalid credential errors to go unnoticed in this task. Users would believe everything was configured correctly and then sign in would fail with 'invalid credentials'. This adds a specific bind check, plus catches errors connecting to the server. Also, specs :)
-
- 03 Nov, 2016 1 commit
-
-
Robert Speicher authored
This was the only thing using the `sdoc` gem, which was blocking another gem from updating.
-
- 01 Nov, 2016 1 commit
-
-
Drew Blessing authored
-
- 21 Oct, 2016 1 commit
-
-
Rémy Coutable authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-
- 20 Oct, 2016 1 commit
-
-
Valery Sizov authored
-
- 13 Oct, 2016 2 commits
-
-
Rémy Coutable authored
Also add a safeguard for non-CI env. Signed-off-by: Rémy Coutable <remy@rymai.me>
-
Rémy Coutable authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-
- 11 Oct, 2016 1 commit
-
-
Rémy Coutable authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-