-
Georges Racinet authored
The ultimate goal being to be able to compare HGitaly responses to Gitaly responses, this defines concepts to describe Gitaly installations and adds a discovery system. A Gitaly installation is at this point a directory with all the compiled executables and a `ruby` subdirectory for the gitaly-ruby side. The CI will run on a base image with an existing installation, which will be specified by passing the `GITALY_INSTALL_DIR` environment variable, interpreted by these tests as a strong promise, and triggering the coverage of `tests_with_gitaly` in the `run-all-tests` script. Otherwise, the tests are able to detect the common case where HGitaly is part of a HDK workspace and use the standard location for the Gitaly checkout (after minimal checking).
Georges Racinet authoredThe ultimate goal being to be able to compare HGitaly responses to Gitaly responses, this defines concepts to describe Gitaly installations and adds a discovery system. A Gitaly installation is at this point a directory with all the compiled executables and a `ruby` subdirectory for the gitaly-ruby side. The CI will run on a base image with an existing installation, which will be specified by passing the `GITALY_INSTALL_DIR` environment variable, interpreted by these tests as a strong promise, and triggering the coverage of `tests_with_gitaly` in the `run-all-tests` script. Otherwise, the tests are able to detect the common case where HGitaly is part of a HDK workspace and use the standard location for the Gitaly checkout (after minimal checking).