- Sep 04, 2019
-
-
dineshpanda authored
-
- Sep 03, 2019
-
-
Extends the permission of $CI_REGISTRY_USER to allow them to delete tags in addition to just pushing. https://gitlab.com/gitlab-org/gitlab-ce/issues/40096
-
- Aug 01, 2019
-
-
https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/3809Valery Sizov authored
Introducing Docker Registry replication
-
- Mar 18, 2019
-
-
Peter Bábics authored
-
- Feb 07, 2019
-
-
Dmitriy Zaporozhets authored
Signed-off-by:
Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- Nov 01, 2018
-
-
George Tsiolis authored
-
- Aug 01, 2018
-
-
Kamil Trzcińśki authored
-
- Jul 16, 2018
-
-
gfyoung authored
For directories application_settings --> labels. Partially addresses #47424.
-
- Apr 10, 2018
-
-
Mayra Cabrera authored
-
- Apr 07, 2018
-
-
Mayra Cabrera authored
- Adds a default on expires_at datetime - Modifies deploy tokens views to handle default expires at value - Use datetime_with_timezone where possible - Remove unused scopes
-
Mayra Cabrera authored
Also, fixes broken specs
-
Mayra Cabrera authored
Also: - Changes scopes from serializer to use boolean columns - Fixes broken specs
-
-
Mayra Cabrera authored
- When using 'read_repo' password and project are sent, so we used both of them to fetch for the token - When using 'read_registry' only the password is sent, so we only use that for fetching the token
-
- Feb 02, 2018
-
-
Mario de la Ossa authored
-
- Oct 10, 2017
-
-
Vratislav Kalenda authored
-
- Oct 08, 2017
-
-
Vratislav Kalenda authored
-
Vratislav Kalenda authored
-
- Aug 31, 2017
-
-
Sean McGivern authored
The initializers including this were doing so at the top level, so every object loaded after them had a `current_application_settings` method. However, if someone had rack-attack enabled (which was loaded before these initializers), it would try to load the API, and fail, because `Gitlab::CurrentSettings` didn't have that method. To fix this: 1. Don't include `Gitlab::CurrentSettings` at the top level. We do not need `Object.new.current_application_settings` to work. 2. Make `Gitlab::CurrentSettings` explicitly `extend self`, as we already use it like that in several places. 3. Change the initializers to use that new form.
-
- Aug 07, 2017
-
-
Lin Jen-Shin authored
Also fix the test because we no longer have :empty_project, just use :project is the same as before
-
- May 29, 2017
-
-
Jean Praloran authored
-
Jean Praloran authored
-
Jean Praloran authored
-
jean authored
-
- Mar 31, 2017
-
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
- Mar 30, 2017
-
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
Because we do not have yet two way communication between container registry and GitLab, we need to eagerly create a new container repository objects in database. We now do that after user/build successfully authenticates a push action using auth service.
-
- Mar 29, 2017
-
-
Grzegorz Bizon authored
Comment explains why we still have authentication without user object there. The legacy authentication mechanism should be removed in 10.0.
-
Grzegorz Bizon authored
-
- Mar 23, 2017
-
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
- Mar 22, 2017
-
-
Grzegorz Bizon authored
[ci skip]
-
- Mar 21, 2017
-
-
Andre Guedes authored
Conflicts: db/schema.rb
-
- Feb 23, 2017
-
-
Douwe Maan authored
-
- Feb 22, 2017
-
-
Andre Guedes authored
-
Andre Guedes authored
- Adds Registry events API endpoint - Adds container_images_repository and container_images models - Changes JWT authentication to allow multi-level scopes - Adds services for container image maintenance
-
- Feb 03, 2017
-
-
Adam Pahlevi authored
add complete changelog for !8949
-
- Nov 09, 2016
-
-
Alejandro Rodriguez authored
Restore unauthenticated access to public container registries Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/24284 See merge request !2025 Signed-off-by:
Rémy Coutable <remy@rymai.me>
-
Douwe Maan authored
Ensure external users are not able to clone disabled repositories. Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/23788 See merge request !2017 Signed-off-by:
Rémy Coutable <remy@rymai.me>
-