delta/gitlab/gitlab-ce.git/lib/api/internal.rb, branch fix/serialized-commit-path

Record and show last used date of SSH Keys

2017-01-08T17:15:39+00:00

Addresses: Issue #13810

1. Adds a last_used_at attribute to the Key table/model
2. Update a key's last_used_at whenever it gets used
3. Display how long ago an ssh key was last used

Accept environment variables from the `pre-receive` script.

2016-12-16T18:02:25+00:00

1. Starting version 2.11, git changed the way the pre-receive flow works.

  - Previously, the new potential objects would be added to the main repo. If the
    pre-receive passes, the new objects stay in the repo but are linked up. If
    the pre-receive fails, the new objects stay orphaned in the repo, and are
    cleaned up during the next `git gc`.

  - In 2.11, the new potential objects are added to a temporary "alternate object
    directory", that git creates for this purpose. If the pre-receive passes, the
    objects from the alternate object directory are migrated to the main repo. If
    the pre-receive fails the alternate object directory is simply deleted.

2. In our workflow, the pre-recieve script (in `gitlab-shell) calls the
   `/allowed` endpoint, which calls out directly to git to perform
   various checks. These direct calls to git do _not_ have the necessary
   environment variables set which allow access to the "alternate object
   directory" (explained above). Therefore these calls to git are not able to
   access any of the new potential objects to be added during this push.

3. We fix this by accepting the relevant environment variables
   (GIT_ALTERNATE_OBJECT_DIRECTORIES, GIT_OBJECT_DIRECTORY) on the
   `/allowed` endpoint, and then include these environment variables while
   calling out to git.

4. This commit includes (whitelisted) these environment variables while making
   the "force push" check. A `Gitlab::Git::RevList` module is extracted to
   prevent `ForcePush` from being littered with these checks.

Fix POST /internal/allowed to cope with gitlab-shell v4.0.0 project paths

2016-11-16T14:30:56+00:00

gitlab-shell v3.6.6 would give project paths like so:

* namespace/project

gitlab-shell v4.0.0 can give project paths like so:

* /namespace1/namespace2/project
* /namespace/project
* /path/to/repository/storage/namespace1/namespace2/project
* /path/to/repository/storage/namespace/project

Refactor storage path extraction from full repo path

2016-10-28T12:55:55+00:00

Signed-off-by: Dmitriy Zaporozhets

Make internal api work with full repo path instead of name

2016-10-27T13:54:48+00:00

Signed-off-by: Dmitriy Zaporozhets

Handle LFS token creation and retrieval in the same method, and in the same Redis connection.

2016-09-28T17:13:48+00:00

Reset expiry time of token, if token is retrieved again before it expires.

Revert "Revert all changes introduced by https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/6043"

2016-09-19T14:34:32+00:00

This reverts commit 6d43c95b7011ec7ec4600e00bdc8df76bb39813c.

Revert all changes introduced by https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/6043

2016-09-19T11:45:28+00:00

Rename capabilities to authentication_abilities

2016-09-16T09:12:21+00:00

Merge remote-tracking branch 'origin/lfs-support-for-ssh' into per-build-token

2016-09-15T19:16:38+00:00

# Conflicts:
#	app/controllers/projects/git_http_client_controller.rb
#	app/helpers/lfs_helper.rb
#	lib/gitlab/auth.rb
#	spec/requests/lfs_http_spec.rb