| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
Includes catfile cache, as well as fixes to the catfile cache code that
caused it to panic in Gitaly
|
|
|
|
Updates the gitaly client to use path_bytes field instead of the
deprecated path field in list_last_commits_for_tree_response.
Also adds a test to guard against non-utf8 path data
|
|
|
|
|
|
|
|
|
|
The gitaly branch has been merged to master and deleted so
need to use master for now until a release gets out.
|
|
Add `GetArchiveRequest` to git-archive params.
Modifies `Git::Repository#archive_metadata` to append `path`
to `ArchivePrefix` so it'll not hit the cache of repository archive
when it already exists.
|
|
|
|
|
|
This reverts merge request !26026
|
|
|
|
Fixes bug in FindAllTags when using a commit sha as the tagname
would cause an error
|
|
|
|
This version includes the server side feature gates required for
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/25615
|
|
When `force` is set to `true` and `start_branch` is set, the
branch will be ovewritten with the new commit based on the
`HEAD` of the `start_branch`.
This commit includes changes to update the `gitaly-proto` gem.
|
|
In 11.8, we added a fix for the SearchFilesByContent RPC in gitaly to
send back the response in chunks. However, we kept in the old code path
for backwards compatibility. Now that the change is fully deployed, we
can remove that old codepath.
|
|
Adds the ground work for writing into
the merge ref refs/merge-requests/:iid/merge the
merge result between source and target branches of
a MR, without further side-effects such as
mailing, MR updates and target branch changes.
|
|
This fixes gRPC dialing to UNIX domain sockets.
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/53473
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This upgrade moves logic from gitlab-rails to Gitaly, which allowed code
removal too.
|
|
Changelog from gitaly:
** v1.7.0
**** Added
- Add an RPC that allows repository size to be reduced by bulk-removing internal references
https://gitlab.com/gitlab-org/gitaly/merge_requests/990
** v1.6.0
**** Other
- Clean up invalid keep-around refs when performing housekeeping
https://gitlab.com/gitlab-org/gitaly/merge_requests/992
** v1.5.0
**** Added
- Add tls configuration to gitaly golang server
https://gitlab.com/gitlab-org/gitaly/merge_requests/932
**** Fixed
- Fix TLS client code on macOS
https://gitlab.com/gitlab-org/gitaly/merge_requests/994
**** Other
- Update to latest goimports formatting
https://gitlab.com/gitlab-org/gitaly/merge_requests/993
** v1.4.0
**** Added
- Link and Unlink RPCs
https://gitlab.com/gitlab-org/gitaly/merge_requests/986
** v1.3.0
*** Other
- Remove unused bridge_exceptions method
https://gitlab.com/gitlab-org/gitaly/merge_requests/987
- Clean up process documentation
https://gitlab.com/gitlab-org/gitaly/merge_requests/984
|
|
|
|
|
|
|
|
|
|
See https://gitlab.com/gitlab-org/gitaly/blob/master/CHANGELOG.md
|
|
|
|
To make sure GitLab will have the latest Gitaly, the version number has
to be bumped here.
|
|
This will allow changes in Gitaly that will make it fail when running
rspec, to make it to GitLab.
Else Gitaly won't start as it can't reach the broken storage directory.
|
|
|
|
|
|
Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/52235
|
|
Implements list_last_commits_for_tree to communicate with the
ListLastCommitsForTree Gitaly RPC
Bumps the Gitaly server version
Bumps the Gitaly-Proto gem version
|
|
With this action the user can update the execute_filemode of a given file in the repository.
|
|
|
|
Rake tasks cleaning up the Git storage were still using direct disk
access, which won't work if these aren't attached. To mitigate a
migration issue was created.
To port gitlab:cleanup:dirs, and gitlab:cleanup:repos, a new RPC was
required, ListDirectories. This was implemented in Gitaly, through
https://gitlab.com/gitlab-org/gitaly/merge_requests/868.
To be able to use the new RPC the Gitaly server was bumped to v0.120.
This is an RPC that will not use feature gates, as this doesn't scale on
.com so there is no way to test it at scale. Futhermore, we _know_ it
doesn't scale, but this might be a useful task for smaller instances.
Lastly, the tests are slightly updated to also work when the disk isn't
attached. Eventhough this is not planned, it was very little effort and
thus I applied the boy scout rule.
Closes https://gitlab.com/gitlab-org/gitaly/issues/954
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/40529
|
|
|
|
|
|
|
