Age | Commit message (Collapse) | Author |
|
With the ability to do feature-flag-based rollouts of the Git version
our process to upgrade Git versions has become a bit more complex.
Document it so that it's easy to follow.
|
|
There are a number of knobs in Gitaly to tune backpressure Gitaly can impose on services that call it. This commit documents these.
|
|
Document the different ways to access Git installations supported by
Gitaly. Most importantly, this also documents the way our new bundled
Git binaries work and why they were introduced.
|
|
git: Remove support for the Ruby hooks directory
Closes #4006
See merge request gitlab-org/gitaly!4356
|
|
gRPC HealthCheck messages are quite noisy, dominate the log volume in
Gitaly, and usually are not that useful. We now disable them by
default and add documentation on how to enable them.
Closes https://gitlab.com/gitlab-org/gitaly/-/issues/3428
Changelog: changed
|
|
The Ruby hooks directory does not exist anymore, and instead we're using
symlinks to the gitaly-hooks binary. Update our documentation to reflect
that change.
|
|
The docs mentions that hooks belongs to Gitlab Shell but it was changed:
https://gitlab.com/gitlab-org/gitaly/issues/1226
|
|
chore: Add ssh signature test case
See merge request gitlab-org/gitaly!4277
|
|
7b20a6045e8d2a25c86633461c03b13353915643 introduced support for SSH
signatures to the `catfile` package. The GetCommitSignatures RPC uses a
different implementation. This implementation is already compatible with
SSH sigantures, but is not tested with them. This change adds tests
which use SSH signatures.
Changelog: other
|
|
|
|
Update the hooks documentation to reflect the new hooks setup which uses
a temporary directory.
|
|
|
|
|
|
|
|
The hooks documentation does not document the reference-transaction
hook. Add this missing information.
|
|
The hook documentation we have is hard to understand at times, and most
importantly it is out-of-date in many places. Rewrite it to reflect the
current state.
|
|
|
|
While writing docs for gitaly-backup it became clear that using the name
`locator` did not make sense.
This would be a breaking change except that the flag is part of an
experimental feature.
Changelog: changed
|
|
|
|
|
|
Better define 'node' in the design document
See merge request gitlab-org/gitaly!3773
|
|
|
|
Changelog: other
|
|
Changelog: removed
|
|
Because Postgres database is required for tests to pass
we explicitly says about it in the documentation and provide
a simple instruction on how to get one.
The change also updates documentation of the glsql package
to align it with the new approach. The old info that is not
actual anymore is removed.
|
|
Add documentation for pack-object cache
See merge request gitlab-org/gitaly!3636
|
|
Changelog: other
|
|
Changelog: other
|
|
GITALY_SOCKET_PATH, GITALY_LISTEN_ADDR and GITALY_PROMETHEUS_LISTEN_ADDR
were marked as deprecated in eb5b9b3af (Document GITALY_DEBUG, 2017-05-10).
It is time to remove them from the code.
To exclude situation when some configuration values could be overridden
by the env vars by mistake the change removes envconfig.Process call
on the gitaly configuration struct.
|
|
Reference transactions have now been baking for several releases and is
performing well. With backchannel voting having landed in release 13.12,
the last blocker which has kept customers from deploying these has been
removed. As a result, we can now finally drop the feature flag
altogether and always enable reference transactions.
Changelog: changed
|
|
The path re-writer is the go script to re-write imports
in the go source code files, proto files and go.mod file.
The script accepts path to the project dir where go.mod file
locates, current module version and desired module version.
Upgrading a module requires re-generating the gRPC stubs
from proto file that is why the code of the path re-writer
script is imported in a new 'upgrade-module' task which covers
that need.
Part of: https://gitlab.com/gitlab-org/gitaly/-/issues/3177
|
|
This commit adds documentation about the reconciliation jobs the
reconciler schedules to fix various inconsistencies that might happen
in a virtual storage.
|
|
This updates the virtual storage documentation to cover repository
assignments.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Now that we have a single distribution of git across all of GitLab's
official distributions of Gitaly, we are in a nicer position to add
custom patches to git. In order to ensure high standards and assert that
we won't ever start to diverge from upstream, this commit documents the
high bar we want to set ourselves for adding custom patches.
|
|
|
|
|
|
It wasn't clear from the existing checklist item added in
2d9d7f9c9 (Add roll out issue template, 2019-06-11) what the removal
steps are, and what "remove feature flag" meant.
Split this up into steps where we discuss the removal from the
codebase, and what changelog entries we expect there, and then discuss
how to remove the feature via chatops.
|
|
|
|
Amend the docs I added in 86c8480e8 (Feature flag rollout doc: expand
on post-100% steps, 2021-01-12) to mention the example of
0ff3ee285 (Remove on-by-default go_user_delete_{branch,tag} feature
flags, 2021-01-21) instead of fbc9f83ab (Remove Ruby code for 100% on
user_delete_{branch,tag} in Go feature, 2021-01-15).
As noted in 0ff3ee285 what I did in fbc9f83ab was wrong &
dangerous. Let's not recommend it.
|
|
I screwed this up in [1] and [2] and as a result the feature didn't
get enabled 100% on January 14th like I thought, but on January 27th
when the changes [3][4] to remove the feature flag itself went
live ([4] being the relevant change).
1. https://gitlab.com/gitlab-org/gitaly/-/issues/3412#note_485304117
2. https://gitlab.com/gitlab-org/gitaly/-/issues/3413#note_485303898
3. https://gitlab.com/gitlab-org/gitaly/-/merge_requests/3035
4. https://gitlab.com/gitlab-org/gitaly/-/merge_requests/3033
|
|
Re-flow a paragraph I added in 40f953069 (Feature flag rollout doc:
rewrite & make better use of template, 2020-12-15).
|
|
doc: Add documentation on object pools
See merge request gitlab-org/gitaly!3060
|
|
After long rounds of refactoring we finally can remove
git.NewCommand function.
The change also includes removal of the TODO left because
of the NewCommand usage with the global config.Config variable.
And as a final step the doc is updated and now mentions usage
of the git.CommandFactory interface instead of git.NewCommand().
Part of: https://gitlab.com/gitlab-org/gitaly/-/issues/2699
|