BigW Consortium Gitlab
Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
G
gitlab-ce
Project
Overview
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
Registry
Registry
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Commits
Issue Boards
Open sidebar
Forest Godfrey
gitlab-ce
Commits
fca2a752
Commit
fca2a752
authored
Jan 22, 2018
by
Rémy Coutable
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Ensure Gitaly Ruby gems are installed using the correct Gemfile and at the correct location
Signed-off-by:
Rémy Coutable
<
remy@rymai.me
>
parent
ea14c1e6
Show whitespace changes
Inline
Side-by-side
Showing
3 changed files
with
15 additions
and
5 deletions
+15
-5
.gitlab-ci.yml
.gitlab-ci.yml
+1
-1
gitaly-test-build
scripts/gitaly-test-build
+13
-3
prepare_build.sh
scripts/prepare_build.sh
+1
-1
No files found.
.gitlab-ci.yml
View file @
fca2a752
...
@@ -6,7 +6,7 @@ image: "dev.gitlab.org:5005/gitlab/gitlab-build-images:ruby-2.3.6-golang-1.9-git
...
@@ -6,7 +6,7 @@ image: "dev.gitlab.org:5005/gitlab/gitlab-build-images:ruby-2.3.6-golang-1.9-git
-
gitlab-org
-
gitlab-org
.default-cache
:
&default-cache
.default-cache
:
&default-cache
key
:
"
ruby-2
35
-with-yarn"
key
:
"
ruby-2
.3.6
-with-yarn"
paths
:
paths
:
-
vendor/ruby
-
vendor/ruby
-
.yarn-cache/
-
.yarn-cache/
...
...
scripts/gitaly-test-build
View file @
fca2a752
...
@@ -9,11 +9,21 @@ require 'fileutils'
...
@@ -9,11 +9,21 @@ require 'fileutils'
# called 'bundle install' using a different Gemfile, as happens with
# called 'bundle install' using a different Gemfile, as happens with
# gitlab-ce and gitaly.
# gitlab-ce and gitaly.
dir
=
'tmp/tests/gitaly'
tmp_tests_gitaly_dir
=
File
.
expand_path
(
'../tmp/tests/gitaly'
,
__dir__
)
abort
'gitaly build failed'
unless
system
(
'make'
,
chdir:
dir
)
# Use the top-level bundle vendor folder so that we don't reinstall gems twice
bundle_vendor_path
=
File
.
expand_path
(
'../vendor'
,
__dir__
)
env
=
{
# This ensure the `clean` config set in `scripts/prepare_build.sh` isn't taken into account
'BUNDLE_IGNORE_CONFIG'
=>
'true'
,
'BUNDLE_GEMFILE'
=>
File
.
join
(
tmp_tests_gitaly_dir
,
'ruby'
,
'Gemfile'
),
'BUNDLE_FLAGS'
=>
"--jobs=4 --path=
#{
bundle_vendor_path
}
--retry=3"
}
abort
'gitaly build failed'
unless
system
(
env
,
'make'
,
chdir:
tmp_tests_gitaly_dir
)
# Make the 'gitaly' executable look newer than 'GITALY_SERVER_VERSION'.
# Make the 'gitaly' executable look newer than 'GITALY_SERVER_VERSION'.
# Without this a gitaly executable created in the setup-test-env job
# Without this a gitaly executable created in the setup-test-env job
# will look stale compared to GITALY_SERVER_VERSION.
# will look stale compared to GITALY_SERVER_VERSION.
FileUtils
.
touch
(
File
.
join
(
dir
,
'gitaly'
),
mtime:
Time
.
now
+
(
1
<<
24
))
FileUtils
.
touch
(
File
.
join
(
tmp_tests_gitaly_
dir
,
'gitaly'
),
mtime:
Time
.
now
+
(
1
<<
24
))
scripts/prepare_build.sh
View file @
fca2a752
...
@@ -3,7 +3,7 @@
...
@@ -3,7 +3,7 @@
export
SETUP_DB
=
${
SETUP_DB
:-
true
}
export
SETUP_DB
=
${
SETUP_DB
:-
true
}
export
CREATE_DB_USER
=
${
CREATE_DB_USER
:-
$SETUP_DB
}
export
CREATE_DB_USER
=
${
CREATE_DB_USER
:-
$SETUP_DB
}
export
USE_BUNDLE_INSTALL
=
${
USE_BUNDLE_INSTALL
:-
true
}
export
USE_BUNDLE_INSTALL
=
${
USE_BUNDLE_INSTALL
:-
true
}
export
BUNDLE_INSTALL_FLAGS
=
"--without
production --jobs
$(
nproc
)
--path vendor --retry
3 --quiet"
export
BUNDLE_INSTALL_FLAGS
=
"--without
=production --jobs=
$(
nproc
)
--path=vendor --retry=
3 --quiet"
if
[
"
$USE_BUNDLE_INSTALL
"
!=
"false"
]
;
then
if
[
"
$USE_BUNDLE_INSTALL
"
!=
"false"
]
;
then
bundle
install
--clean
$BUNDLE_INSTALL_FLAGS
&&
bundle check
bundle
install
--clean
$BUNDLE_INSTALL_FLAGS
&&
bundle check
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment