2017-07-31 09:17:14 -04:00
|
|
|
#!/usr/bin/env ruby
|
|
|
|
|
2017-08-03 06:15:08 -04:00
|
|
|
require 'fileutils'
|
|
|
|
|
2018-05-14 04:10:29 -04:00
|
|
|
require_relative 'gitaly_test'
|
|
|
|
|
2017-07-31 09:17:14 -04:00
|
|
|
# This script assumes tmp/tests/gitaly already contains the correct
|
|
|
|
# Gitaly version. We just have to compile it and run its 'bundle
|
2018-05-14 04:10:29 -04:00
|
|
|
# install'. We have this separate script for that to avoid bundle
|
|
|
|
# poisoning in CI. This script should only be run in CI.
|
|
|
|
class GitalyTestBuild
|
|
|
|
include GitalyTest
|
2017-07-31 09:17:14 -04:00
|
|
|
|
2018-05-14 04:10:29 -04:00
|
|
|
def run
|
|
|
|
abort 'gitaly build failed' unless system(env, 'make', chdir: tmp_tests_gitaly_dir)
|
2017-08-03 06:15:08 -04:00
|
|
|
|
2018-05-14 04:10:29 -04:00
|
|
|
check_gitaly_config!
|
2018-01-22 05:13:33 -05:00
|
|
|
|
2018-05-14 04:10:29 -04:00
|
|
|
# Starting gitaly further validates its configuration
|
|
|
|
pid = start_gitaly
|
|
|
|
Process.kill('TERM', pid)
|
2018-01-22 05:13:33 -05:00
|
|
|
|
2018-05-14 04:10:29 -04:00
|
|
|
# Make the 'gitaly' executable look newer than 'GITALY_SERVER_VERSION'.
|
|
|
|
# Without this a gitaly executable created in the setup-test-env job
|
|
|
|
# will look stale compared to GITALY_SERVER_VERSION.
|
|
|
|
FileUtils.touch(File.join(tmp_tests_gitaly_dir, 'gitaly'), mtime: Time.now + (1 << 24))
|
|
|
|
end
|
|
|
|
end
|
2017-08-03 06:15:08 -04:00
|
|
|
|
2018-05-14 04:10:29 -04:00
|
|
|
GitalyTestBuild.new.run
|